GNOME Bugzilla – Bug 405496
crash in Passwords and Encryption Keys: Open multiply "Find Remo...
Last modified: 2007-04-06 15:26:19 UTC
What were you doing when the application crashed? Open multiply "Find Remote Keys" dialogs. Searchstring was "janek thomaschewski" Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 83623936 vsize: 0 resident: 83623936 share: 0 rss: 16642048 rss_rlim: 0 CPU usage: start_time: 1170878408 rtime: 0 utime: 253 stime: 0 cutime:217 cstime: 0 timeout: 36 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/local/bin/seahorse' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226238288 (LWP 10208)] [New Thread -1268372576 (LWP 10224)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 108832
Thread 2 (Thread -1268372576 (LWP 10224))
Even if version here says 0.9.7 it is actually "seahorse 0.9.10" (from the about dialog).
Hmmm, this looks like a bug in libsoup. Do you have time to install the debug symbols for libsoup2 and duplicate this bug. The resulting stack trace will help us find this problem. Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hi, added the repo for the edgy -dbg packages, and installed the libsoup2 one. This is the output, when it now crashes from Bug-Buddy: ############################### Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 82706432 vsize: 0 resident: 82706432 share: 0 rss: 16179200 rss_rlim: 0 CPU usage: start_time: 1171391563 rtime: 0 utime: 237 stime: 0 cutime:212 cstime: 0 timeout: 25 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/local/bin/seahorse' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1226352976 (LWP 10658)] [New Thread -1268483168 (LWP 10675)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 110448
Thread 2 (Thread -1268483168 (LWP 10675))
I had 2 search windows open. Hope this helps
*** This bug has been marked as a duplicate of 404034 ***