Possibly related to this - gnome-keyring-daemon *sometimes* dies if left running overnight. For example yesterday afternoon I had this:
> set | grep SSH
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SSH_AUTH_SOCK=/tmp/keyring-y0Zso0/ssh
> fuser $SSH_AUTH_SOCK
2674
> ps h `fuser $SSH_AUTH_SOCK`
2674 ? S 0:37 /usr/bin/gnome-keyring-daemon -d --login
All working nicely. This morning I got:
> set | grep SSH
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SSH_AUTH_SOCK=/tmp/keyring-y0Zso0/ssh
> fuser $SSH_AUTH_SOCK
which means the gnome-keyring-daemon process has died.
It seems like the process dies (or is killed) when the screensaver is unlocked in the morning rather than during the night. (screensaver unlock doesn't always do that though).
Possibly related to this - gnome-keyring- daemon *sometimes* dies if left running overnight. For example yesterday afternoon I had this:
> set | grep SSH ASKPASS= /usr/libexec/ openssh/ gnome-ssh- askpass AUTH_SOCK= /tmp/keyring- y0Zso0/ ssh
SSH_
SSH_
> fuser $SSH_AUTH_SOCK gnome-keyring- daemon -d --login
2674
> ps h `fuser $SSH_AUTH_SOCK`
2674 ? S 0:37 /usr/bin/
All working nicely. This morning I got:
> set | grep SSH ASKPASS= /usr/libexec/ openssh/ gnome-ssh- askpass AUTH_SOCK= /tmp/keyring- y0Zso0/ ssh
SSH_
SSH_
> fuser $SSH_AUTH_SOCK
which means the gnome-keyring- daemon process has died.
It seems like the process dies (or is killed) when the screensaver is unlocked in the morning rather than during the night. (screensaver unlock doesn't always do that though).
--
Ian