Bug 386929 – crash in Encryption Keys: USB Harddisk - change fr...

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 386929 - crash in Encryption Keys: USB Harddisk - change fr...


Summary:	crash in Encryption Keys: USB Harddisk - change fr...


Status:	RESOLVED DUPLICATE of bug 353127

Product:	seahorse
Classification:	Applications
Component:	general
Version:	0.9.5
Hardware:	Other All

Importance:	High critical
Target Milestone:	1.0.0
Assigned To:	Seahorse Maintainer
QA Contact:	Seahorse Maintainer

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-17 20:48 UTC by limbacs
Modified:	2007-01-07 18:28 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description limbacs 2006-12-17 20:48:50 UTC

What were you doing when the application crashed?
USB Harddisk - change from a subfolder  back to folder above.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 107556864 vsize: 0 resident: 107556864 share: 0 rss: 17858560 rss_rlim: 0
CPU usage: start_time: 1166388318 rtime: 0 utime: 199 stime: 0 cutime:186 cstime: 0 timeout: 13 it_real_value: 0 frequency: 0

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 -1225824064 (LWP 24523)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 94949

Thread 1 (Thread -1225824064 (LWP 24523))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 strcmp
from /lib/tls/i686/cmov/libc.so.6
#5 _gtk_file_system_model_path_do
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_file_chooser_default_new
from /usr/lib/libgtk-x11-2.0.so.0
#7 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#8 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#9 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#10 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#11 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#12 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#13 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#14 gtk_dialog_run
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
#16 ??
#17 ??
#18 ??
#19 ??
#20 ??
#21 ??
#22 ??
#0 __kernel_vsyscall

Comment 1 Adam Schreiber 2006-12-17 20:56:03 UTC

What were you actually doing in seahorse when it crashed?  Were you browsing for a file to import?

Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a more useful description to 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. Thanks in advance!

Comment 2 limbacs 2006-12-17 22:42:23 UTC

I tried to export my first generated Keypair as Backup on this USB Harddisk.

Comment 3 Stef Walter 2006-12-22 02:30:31 UTC

Thanks for reporting this, but this doesn't look like a seahorse bug. Probably a bug in the gtk+ library that handles the file chooser. But in order to confirm that we'll need a stack trace, as Adam noted.

Comment 4 palfrey 2007-01-07 18:28:47 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 353127 ***