GNOME Bugzilla – Bug 497565
crash in Open Folder: Tried to open properties...
Last modified: 2007-12-30 01:28:23 UTC
Version: 2.18.3 What were you doing when the application crashed? Tried to open properties window (from "properties" command in context menu) on a removable USB flash drive (which also seems to be recognized as a mp3 type device, rather than just a generic USB flash drive). Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 76091392 vsize: 76091392 resident: 25133056 share: 14938112 rss: 25133056 rss_rlim: 4294967295 CPU usage: start_time: 1195273358 rtime: 419 utime: 390 stime: 29 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e136b0 (LWP 4829)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178272
Thread 1 (Thread 0xb6e136b0 (LWP 4829))
----------- .xsession-errors (20 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** (update-notifier:4022): WARNING **: no cdrom: disk --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, the 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. Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible? Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance! [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui. More details can be found here: http://live.gnome.org/GettingTraces
(In reply to comment #1) > Thanks for taking the time to report this bug. > Unfortunately, the 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. > > Could you please help fixing this by installing some debugging packages [1], > start the application as normal, and try to reproduce the crash, if possible? > > Once bug-buddy pops up, you can find the stacktrace in the 'Details', now > containing way more information. Please copy that stacktrace and paste it as a > comment here. Thanks in advance! > > [1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, > libgnome, and libgnomeui. > > More details can be found here: http://live.gnome.org/GettingTraces > Thanks for the help. Sorry to take so long to get back to this. I downloaded the debugging packages. But couldn't find the exact packages for some of the programs you mention: glib2, gtk2, pango, gnome-vfs2. For these I downloaded instead: libglib2.0-0-dbg libgtk2.0-0-dbg libpango1.0-0-dbg libgnomevfs2-0-dbg. Also, for libgnome, I couldn't find anything that looked like an appropriate debugging package. I'm using Debian Testing/Lenny, but I'm really a newbie at this stuff. I can consistently reproduce the crash every time. However, when nautilus crashes now, bug-buddy no longer launches, I don't know why. Finally, I'm also experiencing the same type of crash when I try to launch the properties window on pdf and avi files. How should I proceed from here?
http://live.gnome.org/GettingTraces/Details describes how to get a stacktrace in gdb, but it's a bit more technical. properties: probably a duplicate of bug 440988 which has been fixed in the meantime.
I installed nautilus 2.20, from Debian Unstable, and this seems to have fixed my issues with properties, so it seems like my bug probably is a duplicate.
thanks for the feedback, seems like it is definitely a duplicate of bug 440988.
*** This bug has been marked as a duplicate of 440988 ***