** Description changed: - Binary package hint: seahorse + Binary package hint: gnome-keyring - After resume from hibernate (and not suspend) seahorse-daemon and - seahorse-agent processes are not running, and there is no other ssh- - agent available making it annoying to use ssh, and impossible to use - sftp mounts in nautilus. + 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. - Steps to reproduce: - - 1- ps x | grep seahorse - 2- hibernate and resume (I use gnome-power-manager) - 3- ps x | grep seahorse - - Step 3 returns nothing for me. Step 1 returns something like: - 9554 ? Ss 0:00 seahorse-agent - 9560 ? Ss 0:00 seahorse-daemon - - This is in Ubuntu 8.04, with latest updates. Seahorse version is - 2.22.2-0ubuntu1. + 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). + 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.
** Description changed: 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). + 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. + 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. -- no ssh-agent after resume from hibernate https://bugs.launchpad.net/bugs/268141 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
