GNOME Bugzilla – Bug 374117
crash in Encryption Keys: Criando uma chave ssh, m...
Last modified: 2006-11-23 17:13:02 UTC
What were you doing when the application crashed? Criando uma chave ssh, mais precisamente quando eu configuro o computador que irei acessar Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 64839680 vsize: 0 resident: 64839680 share: 0 rss: 18931712 rss_rlim: 0 CPU usage: start_time: 1163293902 rtime: 0 utime: 2250 stime: 0 cutime:478 cstime: 0 timeout: 1772 it_real_value: 0 frequency: 202 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 -1226504000 (LWP 6773)] [New Thread -1239581792 (LWP 7190)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 85628
Thread 1 (Thread -1226504000 (LWP 6773))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Also, can you please translate the description to English? Thanks in advance!
(In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Can you get us a stack trace with debugging symbols? Please see > http://live.gnome.org/GettingTraces for more information on how to do so. > Also, can you please translate the description to English? > Thanks in advance! > I was creating a ssh key. When the software asked me to configure a computer to use with this ssh key, then the software crashed. About the stack trace i'll try to get it. sorry by my english
i installed the package seahorse-dbgsym and i crashed seahorse again. here is all information. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 43003904 vsize: 0 resident: 43003904 share: 0 rss: 15548416 rss_rlim: 0 CPU usage: start_time: 1163733309 rtime: 0 utime: 918 stime: 0 cutime:275 cstime: 0 timeout: 643 it_real_value: 0 frequency: 182 Backtrace was generated from '/usr/bin/seahorse' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1225750336 (LWP 7400)] [New Thread -1238824032 (LWP 7418)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 87111
Thread 1 (Thread -1225750336 (LWP 7400))
Thanks for reporting this bug and the detailed stack trace. I think this has been fixed in the latest version of seahorse. If you have time and ability, could you build version 0.9.7 and see if the bug is gone? http://ftp.gnome.org/pub/GNOME/sources/seahorse/0.9/seahorse-0.9.7.tar.gz *** This bug has been marked as a duplicate of 363282 ***