Based on the behavior I've observed, I think it's possible that there are two bugs in play here, and fixing one has revealed the other one.
I'm running Xubuntu 14.04. Before this update, starting my terminal from the applications menu yielded a shell with SSH_AUTH_SOCK correctly pointing at gnome-keyring, while starting my terminal from a folder in Thunar file manager yielded a shell with SSH_AUTH_SOCK incorrectly pointing at an ssh-agent instance. The latter didn't work because I only have my ssh key loaded into gnome-keyring. After the update, starting my terminal from the applications menu yields a shell with SSH_AUTH_SOCK correctly pointing at gnome-keyring, while starting my terminal from a folder in Thunar file manager yields a shell with SSH_AUTH_SOCK not set at all. I haven't read the recently released patch yet, so I don't know what it's supposed to do, but it sure looks like it got rid of the ssh-agent instance that I thought I had disabled long ago (great!). That still leaves the problem of why SSH_AUTH_SOCK isn't propagating into my terminal when launched from my file manager. -- 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
