Lars, gnome-keyring-daemon does not set SSH_AUTH_SOCK directly. To get it to work, these things have to happen:
1. Run gnome-keyring-daemon --login This starts the daemon, and is happening automatically on my xubuntu installation. 2. Run gnome-keyring-daemon --start This loads your ssh keys into the already-running daemon, and prints on standard output the shell commands needed to set SSH_AUTH_SOCK. 3. Execute the shell commands that get printed by that last command in a parent shell whose environment variables will be inherited by the processes in your X session. This is how SSH_AUTH_SOCK actually gets set. It is what Mikel is doing in his workaround described in post #8. #3 is definitely not happening in my xubuntu installation. I don't think #2 is happening either, because if it was, I would expect SSH_AUTH_SOCK to be pointing at the gnome-keyring socket (it isn't even set) or else to see the commands for setting it in ~/.xsession-errors (which I don't). -- gnome keyring no longer acts as ssh agent on login https://bugs.launchpad.net/bugs/377467 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
