Comment 3 for bug 377467

Initially I wondered if Ubuntu had changed the order of the X login scripts to invoke Bash before GNOME Keyring, which is why I didn't report the bug upstream.

I still suspect that's the case, but that shouldn't matter: if the GNOME Keyring is being started properly via PAM, then that should happen before Bash is started, and thus SSH_AUTH_SOCK should be set before my ~/.profile is sourced.

The ssh-agent process (pid 3971) above suggests that GNOME Keyring isn't running (or at least hasn't exported the SSH_AUTH_SOCK environment variable) at the time Bash is invoked, so the problem is probably in GNOME Keyring.

Will investigate further when I find the time.