gnome-keyring-daemon cached passwords for SSH keys not working after hibernation

[Borut Mrak]

Binary package hint: gnome-keyring

Description: Ubuntu 8.04
Release: 8.04

gnome-keyring:
  Installed: 2.22.1-1
  Candidate: 2.22.1-1
  Version table:
 *** 2.22.1-1 0
        500 http://de.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

openssh-client:
  Installed: 1:4.7p1-8ubuntu1
  Candidate: 1:4.7p1-8ubuntu1
  Version table:
 *** 1:4.7p1-8ubuntu1 0
        500 http://de.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

When using gnome-keyring-daemon as ssh-agent after first boot, everything is OK.

SSH_AUTH_SOCK=/tmp/keyring-lxl4Ne/ssh

The socket is open by gnome-keyring-daemon. On first SSH connection, the popup asks for the private key password, and caches it for subsequent SSH connections.

After hibernation, however, SSH logins using cached passwords do not work anymore, SSH asks for the key password. Tunneled agent connections also do not work, which is a bigger problem.

SSH_AUTH_SOCK is still set to the same socket, and gnome-keyring-daemon (same PID as before hibernation) still has the socket open, so it should work.

I tried stracing the gnome-keyring-daemon process, but it does not see a connection to the auth socket, so this bug might be in ssh, not gnome-keyring.

If there's any more information I can provide, I'll do my best.

Thanks.
B.

[Borut Mrak (b9bit)]

The system was upgraded from 7.10 about a month ago. Everything was OK there.

[Sebastien Bacher (seb128)]

thank you for your bug report, does changing /apps/gnome-power-manager/lock/gnome_keyring_hibernate in gconf-editor does a difference there?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.