Comment 9 for bug 383926

I don't have a fix for this problem, but I did just find a workaround:

    1) start gnome-keyring-daemon manually; e.g., from a shell prompt, type

             /usr/bin/gnome-keyring-daemon --start

    2) assuming that $SSH_AUTH_SOCK is pointing to the socket created by the old (now defunct) instance of gnome-keyring-daemon, delete the directory containing it, and replace it by a symlink to the directory created by the new instance of gnome-keyring-daemon; for example,

             newsockdir=`ls -dt1 /tmp/keyring* | head -1`
             rm -rf $SSH_AUTH_SOCK
             ln -s $newsockdir $SSH_AUTH_SOCK

This isn't particularly elegant, but it seems to work.