[Bug 268141] Re: no ssh-agent after resume from hibernate
Launchpad has imported 10 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=454186. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2008-07-06T09:15:54+00:00 Julian wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/0 On 2008-08-19T17:35:07+00:00 Julian wrote: I think you need to do something that requires entering ssh key password before suspend as well. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/1 On 2008-11-26T06:45:51+00:00 Julian wrote: Erm, it is still present with Fedora 10. After thorough testing, I found out that this bug is only triggered by hibernation, and that you don't have do to anything prior to it. Do I need to say it makes hibernation pretty much useless, since once you resume you need to input your keyring password every time? Imagine updating a package in cvs like that... Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/9 On 2008-12-13T19:18:07+00:00 Matthias wrote: This is a somewhat confused bug report. If you are talking about ssh, seahorse is not involved, gnome-keyring- daemon is acting as ssh agent. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/10 On 2009-01-13T11:46:54+00:00 Julian wrote: $ gnome-keyring-daemon ** Message: another SSH agent is running at: /tmp/keyring-XZf6Tg/ssh GNOME_KEYRING_SOCKET=/tmp/keyring-SR9ZYj/socket SSH_AUTH_SOCK=/tmp/keyring-SR9ZYj/ssh GNOME_KEYRING_PID=17745 This is what happens if I try to start gnome-keyring-daemon manually after waking up from hibernation. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/11 On 2009-01-13T12:33:24+00:00 Julian wrote: On the other hand, gnome-keyring-daemon does not show up in the list of running processes. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/12 On 2009-02-05T02:26:23+00:00 Ian wrote: 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). -- Ian Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/268141/comments/28 On 2009-02-18T09:05:46+00:00 Julian wrote: I checked with gdb and got the following: Program received signal SIGABRT, Aborted. [Switching to Thread 0x7f68bc4f4950 (LWP 5401)] 0x0032b3432f05 in raise (sig=) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt #0 0x0032b3432f05 in raise (sig=) at ../nptl
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring Importance: Unknown => Critical -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring (Fedora) Status: Confirmed => Fix Released -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
the new version is in jaunty now ** Changed in: gnome-keyring (Ubuntu) Assignee: hyperair (hyperair) => (unassigned) -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
the new version is in jaunty now ** Changed in: gnome-keyring (Ubuntu) Status: Triaged => Fix Released -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sun, 2009-02-01 at 19:09 +, Felipe Figueiredo wrote: > On Sun, Feb 1, 2009 at 3:51 PM, hyperair wrote: > > On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote: > >> Thanks for your work here. The thing is that there is already a new > >> gnome-keyring version available (2.25.5.) which FTBFS for the moment on > >> jaunty. I am currently working with upstream to fix that. I'll integrate > >> your work in the next package for jaunty (this week I think). > >> > > Okay, awesome. How about SRU for Intrepid after that? > > -- > > And Hardy also. > > Thanks hyperair. > You're welcome and here's a Hardy debdiff. -- Chow Loong Jin ** Attachment added: "gnome-keyring_2.22.2-0ubuntu1_2.22.2-0ubuntu2.debdiff" http://launchpadlibrarian.net/21882507/gnome-keyring_2.22.2-0ubuntu1_2.22.2-0ubuntu2.debdiff -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sun, Feb 1, 2009 at 3:51 PM, hyperair wrote: > On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote: >> Thanks for your work here. The thing is that there is already a new >> gnome-keyring version available (2.25.5.) which FTBFS for the moment on >> jaunty. I am currently working with upstream to fix that. I'll integrate >> your work in the next package for jaunty (this week I think). >> > Okay, awesome. How about SRU for Intrepid after that? > -- And Hardy also. Thanks hyperair. -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sun, 2009-02-01 at 17:42 +, Christophe Sauthier (huats) wrote: > Thanks for your work here. The thing is that there is already a new > gnome-keyring version available (2.25.5.) which FTBFS for the moment on > jaunty. I am currently working with upstream to fix that. I'll integrate > your work in the next package for jaunty (this week I think). > Okay, awesome. How about SRU for Intrepid after that? -- Chow Loong Jin -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
Thanks for your work here. The thing is that there is already a new gnome-keyring version available (2.25.5.) which FTBFS for the moment on jaunty. I am currently working with upstream to fix that. I'll integrate your work in the next package for jaunty (this week I think). -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => hyperair (hyperair) -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
And here's a debdiff for Jaunty's gnome-keyring. -- Chow Loong Jin ** Attachment added: "gnome-keyring_2.25.4.1-0ubuntu1_2.25.4.1-0ubuntu2.debdiff" http://launchpadlibrarian.net/21874098/gnome-keyring_2.25.4.1-0ubuntu1_2.25.4.1-0ubuntu2.debdiff -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
..looks like I messed up the previous patch as well. Here's one that's tested (I finally had the sense to test it before uploading). -- Chow Loong Jin ** Attachment removed: "intrepid-debdiff" http://launchpadlibrarian.net/21858990/intrepid-debdiff ** Attachment removed: "intrepid-debdiff" http://launchpadlibrarian.net/21865694/intrepid-debdiff ** Attachment added: "intrepid-debdiff" http://launchpadlibrarian.net/21865887/intrepid-debdiff -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
Okay, it seems that the previous debdiff had a typo in it so it FTBFS'd. Attached is one which shouldn't FTBFS. -- Chow Loong Jin ** Attachment added: "intrepid-debdiff" http://launchpadlibrarian.net/21865694/intrepid-debdiff -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sat, 2009-01-31 at 18:46 +, Felipe Figueiredo wrote: > On Sat, Jan 31, 2009 at 6:07 AM, hyperair wrote: > > On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote: > >> ** Changed in: gnome-keyring > >>Status: New => Fix Released > >> > > Well, it seems upstream fixed the issue in trunk. So we just have to > > wait for the next release of gnome-keyring, and it should be fixed > > there. > > Or someone who has the proper skills gets the patch for that revision, > and tries to use it in ubuntu's version. Maybe then, we can start a > SRU process, if it's applicable. Volunteers? > Alright, here's a debdiff for Intrepid. It still needs to be fixed in Jaunty though, and needs to be approved for Intrepid. -- Chow Loong Jin ** Attachment added: "intrepid-debdiff" http://launchpadlibrarian.net/21858990/intrepid-debdiff -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sat, Jan 31, 2009 at 6:07 AM, hyperair wrote: > On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote: >> ** Changed in: gnome-keyring >>Status: New => Fix Released >> > Well, it seems upstream fixed the issue in trunk. So we just have to > wait for the next release of gnome-keyring, and it should be fixed > there. Or someone who has the proper skills gets the patch for that revision, and tries to use it in ubuntu's version. Maybe then, we can start a SRU process, if it's applicable. Volunteers? -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Sat, 2009-01-31 at 05:24 +, Bug Watch Updater wrote: > ** Changed in: gnome-keyring >Status: New => Fix Released > Well, it seems upstream fixed the issue in trunk. So we just have to wait for the next release of gnome-keyring, and it should be fixed there. -- Chow Loong Jin -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring Status: New => Fix Released -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring (Fedora) Status: Unknown => Confirmed -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
I can confirm that hyperair's workaround works, and it's better, since it requires no user intervention, and it's easier for newbies. I still believe that this is a bug, not a feature, since there appears to be no obvious way to restart the g-k-m after a hibernation/suspend, if the mentioned options are active. I also agree that, for security reasons, the gnome_keyring_hibernate shouldn't come deactivated, because of bug #70752. However, it seems to me that solving bug #70752 by encrypting swap would make hibernation impossible. -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Also affects: gnome-keyring (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=454186 Importance: Unknown Status: Unknown -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
Alright, I can confirm that adjusting the gnome_keyring_hibernate setting to false (unchecked) seems to solve the said issue. My gnome keyring doesn't crash any more upon hibernation. -- Chow Loong Jin -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring Status: Unknown => New -- 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
Re: [Bug 268141] Re: no ssh-agent after resume from hibernate
On Mon, 2009-01-26 at 22:01 +, Sean Hodges wrote: > Work-around works great for me, thanks Felipe. > > Possibly related bug: https://bugs.launchpad.net/ubuntu/+source/gnome- > keyring/+bug/220165. Suggests adjusting the gnome_keyring_hibernate > setting in gconf-editor. > > Related bug at Redhat: > https://bugzilla.redhat.com/show_bug.cgi?id=454186 > > Upstream bug (new): http://bugzilla.gnome.org/show_bug.cgi?id=569253 > I noticed that the bug seems to occur while suspending and not hibernating. Also, when I checked gconf-editor, it would seem as though gnome_keyring_hibernate was set to true, whereas gnome_keyring_suspend was set to false. Perhaps GPM locking the kerying before hibernating is causing the said bug? I'll test with gnome_keyring_hibernate set to false for a while. -- Chow Loong Jin -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs) Status: Confirmed => Triaged ** Also affects: gnome-keyring via http://bugzilla.gnome.org/show_bug.cgi?id=569253 Importance: Unknown Status: Unknown ** Changed in: gnome-keyring (Ubuntu) Target: None => ubuntu-9.04-beta -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
I reproduced this issue on Intrepid by starting gnome-keyring-daemon in the foreground and then sending the computer into hibernate: tstarl...@shimmer:~$ killall gnome-keyring-daemon tstarl...@shimmer:~$ gnome-keyring-daemon -f ** Message: another SSH agent is running at: /tmp/keyring-3pQJ5l/ssh GNOME_KEYRING_SOCKET=/tmp/keyring-idImLe/socket SSH_AUTH_SOCK=/tmp/keyring-idImLe/ssh GNOME_KEYRING_PID=21817 ** ERROR:gkr-keyring.c:504:gkr_keyring_lock: assertion failed: (keyring->password != NULL) Aborted tstarl...@shimmer:~$ The assertion occurred shortly after I clicked "hibernate", I saw it in the terminal before the screen went off. -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
Work-around works great for me, thanks Felipe. Possibly related bug: https://bugs.launchpad.net/ubuntu/+source/gnome- keyring/+bug/220165. Suggests adjusting the gnome_keyring_hibernate setting in gconf-editor. Related bug at Redhat: https://bugzilla.redhat.com/show_bug.cgi?id=454186 Upstream bug (new): http://bugzilla.gnome.org/show_bug.cgi?id=569253 -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
** Changed in: gnome-keyring (Ubuntu) Status: New => Confirmed -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
There's no command line option to pass a directory to g-k-d in runtime. I'll open a wishlist bug to be triaged for this. -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
I found that to use a workaround to restart gnome-keyring-daemon from command line in a way to reuse the existing socket: the env var GNOME_KEYRING_TEST_PATH. This var should be set to the /tmp/keyring- that was previously in use. For example: GNOME_KEYRING_TEST_PATH=/tmp/keyring-pw7JIX/ gnome-keyring-daemon ** Message: another SSH agent is running at: /tmp/keyring-pw7JIX/ssh GNOME_KEYRING_SOCKET=/tmp/keyring-pw7JIX//socket SSH_AUTH_SOCK=/tmp/keyring-pw7JIX//ssh GNOME_KEYRING_PID=24788 When I next try to use a ssh key, it asks to authenticate again (should it?), and it caches the keyphrase again. -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
I originally reported this bug against seahorse, since it appears as argument to ssh-agent in the processes list. I'd like to correct the testcase. Although it happened that seahorse died when I decided to post the bug, I cannot reproduce it, therefore I'm forced to attribute this event to chance. I confirm that the ssh-agent is not functional after hibernate, and now I have a new test-case that I can reproduce at will. Test case: 1- ps x | egrep "agent|keyring" 2- hibernate and thaw 3- ps x | egrep "agent|keyring" Step 1 returns: 7174 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 7243 ?Ss 0:00 /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 7291 ?SL 0:00 /usr/bin/gnome-keyring-daemon Step 3 returns: 7174 ?Ss 0:00 /usr/bin/ssh-agent /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 7243 ?Ss 0:00 /usr/bin/seahorse-agent --execute sh /home/philsf/.xsession 9489 pts/2S+ 0:00 egrep agent|keyring So, gnome-keyring-daemon is the process that dies. I'm assigning the bug to gnome-keyring package. This is gnome-keyring 2.22.2-0ubuntu1. The relevant directories in /tmp (/tmp/ssh-* and /tmp/keyrin*) are not deleted, but the pipe can't be reused without restarting gnome-keyring- daemon, and there's no documentation on how to restart it reusing the existing socket for this reason I can't use the workaround in bug #99065. Also, why does gnome-keyring-daemon crashes in the first place? The following is the only relevant line in $HOME/.xsession-errors ** Message: another SSH agent is running at: /tmp/ssh- UZKukL7062/agent.7062 This appears to be the same message I get from g-k-d, if I try to start it manually after hibernating. The process daemonizes, but there's no ssh-agent to be used: $ ssh localhost Error reading response length from authentication socket. Enter passphrase for key '/home/philsf/.ssh/id_dsa': ** Changed in: gnome-keyring (Ubuntu) Sourcepackagename: seahorse-plugins => gnome-keyring Status: Incomplete => New -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
Could you perhaps try with intrepid? I think upstream won't accept any bugs from older versions anymore, now that 2.24.0 is out. Also, please check if ssh-agent runs on the same pipe after resuming your pc. ** Changed in: seahorse-plugins (Ubuntu) Status: New => Incomplete -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
Reassigning to seahorse-plugins, this is the package where seahorse- agent is in intrepid. ** Changed in: seahorse-plugins (Ubuntu) Sourcepackagename: seahorse => seahorse-plugins Importance: Undecided => Medium -- 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
[Bug 268141] Re: no ssh-agent after resume from hibernate
Related bugs (not dups): bug #99065 and #70752 -- 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
