GNOME Bugzilla – Bug 363282
crash in Encryption Keys: Sending a key to the rem...
Last modified: 2007-03-27 11:41:59 UTC
What were you doing when the application crashed? Sending a key to the remote server with "Configure SSH Key for Login"... Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 48136192 vsize: 0 resident: 48136192 share: 0 rss: 17141760 rss_rlim: 0 CPU usage: start_time: 1161213248 rtime: 0 utime: 1564 stime: 0 cutime:908 cstime: 0 timeout: 656 it_real_value: 0 frequency: 244 Backtrace was generated from '/usr/bin/seahorse' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225832256 (LWP 8914)] [New Thread -1242715232 (LWP 10384)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 77072
Thread 1 (Thread -1225832256 (LWP 8914))
Do you have a moment to run seahorse from a terminal, get the crash to happen again, and post the terminal output at this bug?
Created attachment 75307 [details] Terminal output from seahorse 0.9.5 Sure. This attachment contains the terminal output from the initial start to bug-buddy. The initial report doesn't mention the steps taken to reproduce this bug. This is what I am doing: 1. "Create a new key (Ctrl-N)" 2. Select "SSH Key". 3. Enter e-mail address in "Email address", check "Configure my new key on another computer", then click "Create". 4. Enter a passphrase twice. 5. "Configure SSH Key for Login" window: enter the login name and the server. I have tried with two SSH servers: iroquois.gel.ulaval.ca and anemone.oceanosoft.ca. I have the necessary access on both. Hope this will help.
*** Bug 361824 has been marked as a duplicate of this bug. ***
*** Bug 364813 has been marked as a duplicate of this bug. ***
*** Bug 365806 has been marked as a duplicate of this bug. ***
*** Bug 365895 has been marked as a duplicate of this bug. ***
REOPENing, since the requested information has been provided. Also confirming due to duplicates. (Although the stacktraces are rather short and don't have much information, they are identical with matching descriptions.) From the stacktrace of duplicate bug 364813:
+ Trace 78946
A quick compile of the latest development version appears to fix this problem. I'm running Ubuntu Edgy. Can anybody else confirm that the latest version works for them too? I've filed a bug in Launchpad to investigate further: https://launchpad.net/distros/ubuntu/+source/seahorse/+bug/68691 Thanks.
It seems this was a race condition caused by reloading of the keys from the disk while the 'configure key for SSH login' dialog had a reference to the key. This bug would only show up when creating a key and using the 'Create and configure' button to immediately configure the key in question. Cleaned up a bunch of the loading and reloading code. This should be fixed in HEAD. 2006-11-02 Nate Nielsen <nielsen@memberwebs.com> * libseahorse/seahorse-context.c: * libseahorse/seahorse-context.h: * libseahorse/seahorse-hkp-source.c: * libseahorse/seahorse-key-source.c: * libseahorse/seahorse-key-source.h: * libseahorse/seahorse-ldap-source.c: * libseahorse/seahorse-pgp-source.c: * libseahorse/seahorse-pgp-source.h: * libseahorse/seahorse-server-source.c: * libseahorse/seahorse-ssh-operation.c: * libseahorse/seahorse-ssh-source.c: * libseahorse/seahorse-unknown-source.c: * plugins/applet/seahorse-applet.c: * src/seahorse-gkeyring-item-properties.c: * src/seahorse-gkeyring-operation.c: * src/seahorse-gkeyring-source.c: * src/seahorse-key-properties.c * src/seahorse-key-manager.c: Cleanup the key loading and searching code. Don't unnecessary remove keys from context. Fixes bug #363282
*** Bug 369183 has been marked as a duplicate of this bug. ***
*** Bug 374117 has been marked as a duplicate of this bug. ***
*** Bug 408005 has been marked as a duplicate of this bug. ***
*** Bug 399785 has been marked as a duplicate of this bug. ***
*** Bug 423221 has been marked as a duplicate of this bug. ***