Ubuntu
nautilus-open-terminal package

"open in terminal" does not honour SSH_AUTH_SOCK and GPG_AGENT_INFO environment variables in Ubuntu 14.10

Bug #1411174 reported by Thanos Kyritsis
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gnome-terminal (Ubuntu)
Confirmed
Undecided
Unassigned
nautilus-open-terminal (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Steps to reproduce:

Open a terminal in Unity via the Launcher (or Dash) and ssh into something. The ssh-agent unity keyring dialog will popup asking for the passphrase. Everything's ok.

Now open a terminal via nautilus-open-terminal, for example right click on Desktop -> Open in Terminal and run env. The SSH_AUTH_SOCK and GPG_AGENT_INFO variables are not set. Other env vars are also slightly different but this might not be necessarily a problem. The problem is that trying to ssh somewhere cannot access the already running ssh-agent (unity gnome keyring), ssh will prompt in CLI for the passphrase.

The expected behaviour (at least until 14.04 LTS) was that SSH_AUTH_SOCK and GPG_AGENT_INFO were set when opening the terminal via nautilus "Open in Terminal".

$ lsb_release -rd
Description: Ubuntu 14.10
Release: 14.10

$ apt-cache policy nautilus-open-terminal
nautilus-open-terminal:
  Installed: 0.20-1
  Candidate: 0.20-1

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus-open-terminal (Ubuntu):
status: New → Confirmed
Revision history for this message
Thanos Kyritsis (djart) wrote :

I think this is fixed in Vivid, so perhaps this bug could be closed.

Revision history for this message
Thanos Kyritsis (djart) wrote :

I was wrong, it's still not fixed in Vivid.

Revision history for this message
Michael Tänzer (neoatnhng) wrote :

Also affects the version of the plugin shipped with the gnome-terminal package

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-terminal (Ubuntu):
status: New → Confirmed
Revision history for this message
Simon John (sej7278) wrote :

this behaviour has just started happening in gnome 3.18.0-1 on debian sid, but only for ssh, gpg is still working

Revision history for this message
Simon John (sej7278) wrote :

Does anyone know if the Gnome devs are even looking into this? Its still present in 3.18.2-1 on Debian

I wonder if it would be better filed upstream with Gnome as the Debian/Ubuntu maintainers seem to just package, not patch/fix Gnome. Anyone seen this on non-Debian-based distro's?

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

@Simon:

I proposed a workaround (ugly) in http://askubuntu.com/questions/606451/nautilus-open-in-terminal-extension-will-not-propagate-ssh-auto-sock

A upstream report would be nice; I suspect it could be related to the fact that "run in terminal" is hard coded in gnome (see
https://bugzilla.gnome.org/show_bug.cgi?id=627943 ) or not.

Revision history for this message
Scaler (balaton22) wrote :

I have the same issue with two computers since I switched to 16.04.
No problem when I was on 15.10 or earlier.

Maybe related to this bug? https://bugs.launchpad.net/bugs/1271591

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.