gnome-keyring-daemon is running, but SSH_AUTH_SOCK is not set in the session environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
Fix Released
|
High
|
Martin Pitt |
Bug Description
Binary package hint: gnome-keyring
After starting a new session recently (due to bug 343528), I noticed that my ssh sessions were no longer making use of the GNOME keyring. This seems to be because SSH_AUTH_SOCK is no longer set in the environment of programs running in the session.
It is printed in ~/.xsession-errors:
perseus:[~] grep SSH .xsession-errors
SSH_AUTH_
and setting it in a shell works (ssh then talks to gnome-keyring-
ProblemType: Bug
Architecture: amd64
Date: Tue Jul 21 11:40:41 2009
DistroRelease: Ubuntu 9.10
Package: gnome-keyring 2.27.4-0ubuntu1
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcVersionSign
SourcePackage: gnome-keyring
Uname: Linux 2.6.31-3-generic x86_64
how do you start your command line? gnome-session doesn't have the SSH environment there but gnome-panel has it for example