| 2008-09-09 13:52:44 |
Felipe Figueiredo |
bug |
|
|
added bug |
| 2008-09-09 14:02:44 |
Andreas Moog |
seahorse: importance |
Undecided |
Medium |
|
| 2008-09-09 14:02:44 |
Andreas Moog |
seahorse: bugtargetdisplayname |
seahorse (Ubuntu) |
seahorse-plugins (Ubuntu) |
|
| 2008-09-09 14:02:44 |
Andreas Moog |
seahorse: bugtargetname |
seahorse (Ubuntu) |
seahorse-plugins (Ubuntu) |
|
| 2008-09-09 14:02:44 |
Andreas Moog |
seahorse: statusexplanation |
|
Reassigning to seahorse-plugins, this is the package where seahorse-agent is in intrepid. |
|
| 2008-09-09 14:02:44 |
Andreas Moog |
seahorse: title |
Bug #268141 in seahorse (Ubuntu): "no ssh-agent after resume from hibernate" |
Bug #268141 in seahorse-plugins (Ubuntu): "no ssh-agent after resume from hibernate" |
|
| 2008-09-25 21:58:00 |
Andreas Moog |
seahorse-plugins: status |
New |
Incomplete |
|
| 2008-09-25 21:58:00 |
Andreas Moog |
seahorse-plugins: statusexplanation |
Reassigning to seahorse-plugins, this is the package where seahorse-agent is in intrepid. |
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. |
|
| 2008-09-27 10:53:47 |
Felipe Figueiredo |
seahorse-plugins: status |
Incomplete |
New |
|
| 2008-09-27 10:53:47 |
Felipe Figueiredo |
seahorse-plugins: bugtargetdisplayname |
seahorse-plugins (Ubuntu) |
gnome-keyring (Ubuntu) |
|
| 2008-09-27 10:53:47 |
Felipe Figueiredo |
seahorse-plugins: bugtargetname |
seahorse-plugins (Ubuntu) |
gnome-keyring (Ubuntu) |
|
| 2008-09-27 10:53:47 |
Felipe Figueiredo |
seahorse-plugins: statusexplanation |
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. |
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/2 S+ 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': |
|
| 2008-09-27 10:53:47 |
Felipe Figueiredo |
seahorse-plugins: title |
Bug #268141 in seahorse-plugins (Ubuntu): "no ssh-agent after resume from hibernate" |
Bug #268141 in gnome-keyring (Ubuntu): "no ssh-agent after resume from hibernate" |
|
| 2008-10-28 21:29:27 |
Chow Loong Jin |
gnome-keyring: status |
New |
Confirmed |
|
| 2008-10-28 21:29:27 |
Chow Loong Jin |
gnome-keyring: statusexplanation |
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/2 S+ 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': |
|
|
| 2009-01-26 23:57:37 |
Sebastien Bacher |
gnome-keyring: status |
Confirmed |
Triaged |
|
| 2009-01-26 23:57:37 |
Sebastien Bacher |
gnome-keyring: assignee |
|
desktop-bugs |
|
| 2009-01-26 23:57:51 |
Sebastien Bacher |
bug |
|
|
assigned to gnome-keyring |
| 2009-01-26 23:58:17 |
Sebastien Bacher |
gnome-keyring: milestone |
|
ubuntu-9.04-beta |
|
| 2009-01-27 03:34:19 |
Bug Watch Updater |
gnome-keyring: status |
Unknown |
New |
|
| 2009-01-27 14:42:43 |
Felipe Figueiredo |
bug |
|
|
assigned to gnome-keyring (Fedora) |
| 2009-01-27 21:16:42 |
Bug Watch Updater |
gnome-keyring: status |
Unknown |
Confirmed |
|
| 2009-01-31 05:24:14 |
Bug Watch Updater |
gnome-keyring: status |
New |
Fix Released |
|
| 2009-01-31 19:30:41 |
Chow Loong Jin |
bug |
|
|
added attachment 'intrepid-debdiff' (intrepid-debdiff) |
| 2009-02-01 01:36:27 |
Chow Loong Jin |
bug |
|
|
added attachment 'intrepid-debdiff' (intrepid-debdiff) |
| 2009-02-01 01:57:24 |
Chow Loong Jin |
bug |
|
|
added attachment 'intrepid-debdiff' (intrepid-debdiff) |
| 2009-02-01 11:05:25 |
Chow Loong Jin |
description |
Binary package hint: seahorse
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.
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. |
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).
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. |
|
| 2009-02-01 11:08:04 |
Chow Loong Jin |
description |
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).
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. |
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. |
|
| 2009-02-01 12:03:49 |
Chow Loong Jin |
bug |
|
|
added subscriber Ubuntu Sponsors for main |
| 2009-02-01 12:03:49 |
Chow Loong Jin |
bug |
|
|
added attachment 'gnome-keyring_2.25.4.1-0ubuntu1_2.25.4.1-0ubuntu2.debdiff' (gnome-keyring_2.25.4.1-0ubuntu1_2.25.4.1-0ubuntu2.debdiff) |
| 2009-02-01 14:52:17 |
Chow Loong Jin |
gnome-keyring: assignee |
desktop-bugs |
hyperair |
|
| 2009-02-01 19:42:25 |
Chow Loong Jin |
bug |
|
|
added attachment 'gnome-keyring_2.22.2-0ubuntu1_2.22.2-0ubuntu2.debdiff' (gnome-keyring_2.22.2-0ubuntu1_2.22.2-0ubuntu2.debdiff) |
| 2009-02-12 17:27:30 |
Sebastien Bacher |
gnome-keyring: status |
Triaged |
Fix Released |
|
| 2009-02-12 17:27:30 |
Sebastien Bacher |
gnome-keyring: statusexplanation |
|
the new version is in jaunty now |
|
| 2009-02-12 17:27:38 |
Sebastien Bacher |
gnome-keyring: assignee |
hyperair |
|
|
| 2009-07-29 12:20:51 |
Bug Watch Updater |
gnome-keyring (Fedora): status |
Confirmed |
Fix Released |
|
| 2010-09-16 14:04:11 |
Bug Watch Updater |
gnome-keyring: importance |
Unknown |
Critical |
|
| 2011-02-17 09:21:55 |
Daniel Holbach |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2011-02-17 09:22:04 |
Daniel Holbach |
removed subscriber [DEPRECATED] Ubuntu Sponsors for main |
|
|
|
| 2011-02-21 23:33:33 |
Benjamin Drung |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2017-10-27 04:01:11 |
Bug Watch Updater |
gnome-keyring (Fedora): importance |
Unknown |
Low |
|
