After disabling GNOME Keyring Daemon from GNOME Startup Applications, it now does this:
Mon May 18 10:21:23 EST 2009 profile SSH_AGENT_PID= SSH_AUTH_SOCK= gnome-keyring=19685 ssh-agent=4198,12447 Mon May 18 10:22:04 EST 2009 shrc SSH_AGENT_PID=19724 SSH_AUTH_SOCK=/tmp/ssh-vNoOL19723/agent.19723 gnome-keyring=19685 ssh-agent=4198,12447,19724 SSH_AUTH_SOCK now points to ssh-agent rather than GNOME Keyring daemon. This suggests g-k-d is (now?) split into two halves, and it's only initializing SSH_AUTH_SOCK after the second half starts, further that the GNOME startup applications are running after /etc/gdm/Xsession sources ~/.profile. -- 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
