GNOME Bugzilla – Bug 495918
crash in Computer: Crash of nautilus (debia...
Last modified: 2007-11-13 17:42:08 UTC
Version: 2.18.3 What were you doing when the application crashed? Crash of nautilus (debian unstable I386). Right click on file of name "hello", and asking for properties. "hello" file (test purpose) is a very short file of 2 lines : #!/usr/bin/perl print "hello\n"; Properties are -rwxr-xr-x Runs normally with shell command ./hello It seems that nautilus does not accept shebang perl. Maybe it is a wrong configuration on local machine, but this has never occured under previous versions of nautilus. 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: 74268672 vsize: 74268672 resident: 24842240 share: 15192064 rss: 24842240 rss_rlim: 4294967295 CPU usage: start_time: 1194799381 rtime: 168 utime: 157 stime: 11 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 0xb6de96b0 (LWP 1278)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 177040
Thread 1 (Thread 0xb6de96b0 (LWP 1278))
----------- .xsession-errors (20304 sec old) --------------------- ** 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 ** Message: drive = 0 ** Message: volume = 0 ...Too much output, ignoring rest... --------------------------------------------------
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
Thank you for your answer. I have installed the required debug packages and I hope that no one is missing ! Here you can see the new detailed stacktrace : 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: 74371072 vsize: 74371072 resident: 25137152 share: 15273984 rss: 25137152 rss_rlim: 4294967295 CPU usage: start_time: 1194961985 rtime: 234 utime: 214 stime: 20 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6db26b0 (LWP 25637)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 177419
Thread 1 (Thread 0xb6db26b0 (LWP 25637))
----------- .xsession-errors --------------------- ** 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 Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
This is a debian-specific problem and will be solved by updating. Please ask Debian for updates. *** This bug has been marked as a duplicate of 440988 ***
OK. Thank you for your help.