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 Package: gnome-keyring Status: install ok installed Priority: optional Section: gnome Installed-Size: 3572 Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com> Architecture: amd64 Multi-Arch: foreign Version: 3.10.1-1ubuntu4.1 Depends: dconf-gsettings-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 Pre-Depends: multiarch-support Recommends: libpam-gnome-keyring, libp11-kit-gnome-keyring Breaks: libgnome-keyring0 (<< 3.0), seahorse-plugins (<< 3.0) Conffiles: /etc/xdg/autostart/gnome-keyring-pkcs11.desktop 784b3d1e0681f9bb3c8e88a5dd647f0b /etc/xdg/autostart/gnome-keyring-gpg.desktop 36f92b6ee1ec39fd7a66800ed344b982 /etc/xdg/autostart/gnome-keyring-ssh.desktop 2524e326e3413945eabe06dabadb75e5 /etc/xdg/autostart/gnome-keyring-secrets.desktop 6bbabf4d27046c3bbd4c9081bd9abc4c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1271591 Title: upstart job race prevents gnome-keyring from being ssh agent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1271591/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
