Bug 468727

Description of problem:
When I first login to a GNOME session, if I then SSH to a machine requiring passphrases, GNOME presents a graphical dialog to enter key passphrase.
Thereafter I can SSH to any machine without entering passphrases

When I then hibernate to disk, and then resume, everything has stopped working.

$ printenv  | grep SSH
SSH_AGENT_PID=3185
SSH_AUTH_SOCK=/tmp/keyring-8IVhyB/ssh
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass


The PID there corresponds to an active ssh-agent process


$ pgrep ssh-agent
3185

but the socket is not one owned by the agent


# lsof -p 3185 | grep unix
ssh-agent 3185 berrange    3u  unix 0xf578d6c0           25293 /tmp/ssh-otTzRy3041/agent.3041


As far as I can tell sockets named with /tmp/keyring-XXXX as their prefix are being created by gnome-keyring-daemon. The only instance of gnome-keyring-daemon running on my machine though does not correspond to the socket listed in the environment. The process was also suspiciously created just at the time of resume

# lsof | grep /tmp/keyring-
gnome-key 26566  berrange    8u     unix 0xf6128700              496364 /tmp/keyring-sx4mmd/socket
gnome-key 26566  berrange   14u     unix 0xdec5f500              498334 /tmp/keyring-sx4mmd/socket


I can only guess that gnome-keyring-daemon is crashing at somepoint in hibernate/resume sequence, and getting restarted, but once restarted the SSH functionality is utterly useless since its listening on a different socket.

The only way I can get working SSH agent back now is to logout of GNOME again, defeating the point of having hibernate/resume, because i loose my session.


I also see errors from network manager about broken keyring socket

$ grep keyring ~/.xsession-errors 
** (nm-applet:3292): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-8IVhyB/socket: Connection refused
** (nm-vpnc-auth-dialog:26674): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-8IVhyB/socket: Connection refused
** (nm-vpnc-auth-dialog:26674): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-8IVhyB/socket: Connection refused


This was all working correctly until a week or so ago, but I don't see any updates to gnome-keyring for several months.


Version-Release number of selected component (if applicable):
$ uname -r
2.6.26.6-79.fc9.i686
[berrange@t60wlan ~]$ rpm -q gnome-keyring
gnome-keyring-2.22.3-1.fc9.i386


How reproducible:
Always

Steps to Reproduce:
1. Hibernate to disk
2. Resume from hibernate
3. SSH to a machine using passphrases
  
Actual results:
SSH prompts for passphrase
ssh-add shows no active agent sock

Expected results:
SSH sessions logs in without prompting

Additional info: