Comment 4 for bug 268141

I originally reported this bug against seahorse, since it appears as argument to ssh-agent in the processes list.

I'd like to correct the testcase. Although it happened that seahorse died when I decided to post the bug, I cannot reproduce it, therefore I'm forced to attribute this event to chance.

I confirm that the ssh-agent is not functional after hibernate, and now I have a new test-case that I can reproduce at will.

Test case:
1- ps x | egrep "agent|keyring"
2- hibernate and thaw
3- ps x | egrep "agent|keyring"

Step 1 returns:
 7174 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession
 7243 ? Ss 0:00 /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession
 7291 ? SL 0:00 /usr/bin/gnome-keyring-daemon

Step 3 returns:
7174 ? Ss 0:00 /usr/bin/ssh-agent /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession
7243 ? Ss 0:00 /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession
9489 pts/2 S+ 0:00 egrep agent|keyring

So, gnome-keyring-daemon is the process that dies. I'm assigning the bug to gnome-keyring package. This is gnome-keyring 2.22.2-0ubuntu1.

The relevant directories in /tmp (/tmp/ssh-* and /tmp/keyrin*) are not deleted, but the pipe can't be reused without restarting gnome-keyring-daemon, and there's no documentation on how to restart it reusing the existing socket for this reason I can't use the workaround in bug #99065.

Also, why does gnome-keyring-daemon crashes in the first place? The following is the only relevant line in $HOME/.xsession-errors

** Message: another SSH agent is running at: /tmp/ssh-UZKukL7062/agent.7062

This appears to be the same message I get from g-k-d, if I try to start it manually after hibernating. The process daemonizes, but there's no ssh-agent to be used:

$ ssh localhost
Error reading response length from authentication socket.
Enter passphrase for key '/home/philsf/.ssh/id_dsa':