Binary package hint: gnome-keyring
When gconf key /apps/gnome-power-manager/lock/gnome_keyring_suspend is set to true, and GNOME Keyring's password is blank, gnome-keyring crashes with a failed assertion when attempting to hibernate the system. The same thing happens when /apps/gnome-power-manager/lock/gnome_keyring_suspend is set to true, during an attempt to suspend.
TEST CASE:
1. On a system where suspend works, set /apps/gnome-power-manager/lock/gnome_keyring_suspend to true.
2. SSH into a known system using a public key that is protected by a passphrase. Note that GNOME Keyring remembers the passphrase (or prompts you with the GUI). Alternatively, run 'ps aux | grep gnome-keyring-daemon' and note that there is a process by the name of gnome-keyring-daemon running.
3. Suspend the system (using Fast-User-Switch-Applet)
4. Resume the system
5. Attempt #2 again. Notice that SSH now prompts you for a passphrase from within the terminal, and it is not remembered. Alternatively, run 'ps aux | grep gnome-keyring' and note that gnome-keyring-daemon has disappeared from the processes list.
Description of problem:
After resume from either suspend or hibernate, seahorse agent does not ask for
keyring password, so for instance to commit to Fedora cvs I have to enter the
ssh keys password a few times. Before the resume a window pops out and the
password is required only once.
Version-Release number of selected component (if applicable):
2.22.2-1.fc9
How reproducible:
every time
Steps to Reproduce:
1. suspend/hibernate the machine
2. resume
3. do something that requires entering ssh key password
Actual results:
password prompt appears in the console every time ssh key is needed
Expected results:
a window pops out and asks for password only once
Additional info:
I don't know if it's related, but ssh-add does not work either (says “Could not
open a connection to your authentication agent.”), so there is really no way to
avoid the need for entering the password several times, apart from reboot.