desktop-packages team mailing list archive

[Launchpad Bug Tracker <1411174@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: gnome-terminal (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1411174

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

Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in nautilus-open-terminal package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1411174/+subscriptions