I just encountered this problem and eventually found this bug.
I see exactly the behaviour described above - starting a terminal with
ctrl-alt-T gets the correct SSH_AUTH_SOCK, otherwise it's wrong.
dpkg -s gnome-keyring confirms that the fix above is
already running on my system:
I just encountered this problem and eventually found this bug.
I see exactly the behaviour described above - starting a terminal with
ctrl-alt-T gets the correct SSH_AUTH_SOCK, otherwise it's wrong.
dpkg -s gnome-keyring confirms that the fix above is
already running on my system:
% dpkg -s gnome-keyring -backend | gsettings-backend, libc6 (>= 2.15), libcap-ng0, libdbus-1-3 (>= 1.1.1), libgck-1-0 (>= 3.3.90), libgcr-base-3-1 (>= 3.8.0), libgcrypt11 (>= 1.5.1), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.0.0), gcr (>= 3.4), dbus-x11, p11-kit (>= 0.16), libcap2-bin gnome-keyring, libp11- kit-gnome- keyring autostart/ gnome-keyring- pkcs11. desktop 784b3d1e0681f9b b3c8e88a5dd647f 0b autostart/ gnome-keyring- gpg.desktop 36f92b6ee1ec39f d7a66800ed344b9 82 autostart/ gnome-keyring- ssh.desktop 2524e326e341394 5eabe06dabadb75 e5 autostart/ gnome-keyring- secrets. desktop 6bbabf4d27046c3 bbd4c9081bd9abc 4c
Package: gnome-keyring
Status: install ok installed
Priority: optional
Section: gnome
Installed-Size: 3572
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Multi-Arch: foreign
Version: 3.10.1-1ubuntu4.1
Depends: dconf-gsettings
Pre-Depends: multiarch-support
Recommends: libpam-
Breaks: libgnome-keyring0 (<< 3.0), seahorse-plugins (<< 3.0)
Conffiles:
/etc/xdg/
/etc/xdg/
/etc/xdg/
/etc/xdg/