GNOME Bugzilla – Bug 479483
crash when viewing file information
Last modified: 2007-11-18 11:55:44 UTC
Version: 2.18.3 What were you doing when the application crashed? listen to music with banshee Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-486 #1 Wed Jul 11 03:17:09 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Rezlooks-Watercolor Icon Theme: Tango Memory status: size: 66207744 vsize: 66207744 resident: 24363008 share: 15032320 rss: 24363008 rss_rlim: 4294967295 CPU usage: start_time: 1190541739 rtime: 775 utime: 654 stime: 121 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 -1226766672 (LWP 9572)] [New Thread -1259508848 (LWP 11181)] (no debugging symbols found) 0xb7fb57f2 in ?? () from /lib/ld-linux.so.2
+ Trace 164818
Thread 1 (Thread -1226766672 (LWP 9572))
----------- .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.0/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
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
*** Bug 479761 has been marked as a duplicate of this bug. ***
*** Bug 479954 has been marked as a duplicate of this bug. ***
*** Bug 480114 has been marked as a duplicate of this bug. ***
*** Bug 480960 has been marked as a duplicate of this bug. ***
*** Bug 481476 has been marked as a duplicate of this bug. ***
*** Bug 480870 has been marked as a duplicate of this bug. ***
I had about the same issue on debian while trying to get info on some files in nautilus (see dupe bug #480960, sorry) with the libgtk2.0-0 and gtk2-engines-pixbuf packages from sid/unstable installed (on top of a lenny/testing system). After reverting to testing versions of these packages (2.10.13-1 instead of 2.12.0-2), nautilus doesn't crash getting info on some files anymore.
*** Bug 486306 has been marked as a duplicate of this bug. ***
Another case of Bug 440988?
*** Bug 496037 has been marked as a duplicate of this bug. ***
*** Bug 497854 has been marked as a duplicate of this bug. ***
*** Bug 497852 has been marked as a duplicate of this bug. ***
*** Bug 497835 has been marked as a duplicate of this bug. ***
*** Bug 497811 has been marked as a duplicate of this bug. ***
*** Bug 497809 has been marked as a duplicate of this bug. ***
*** Bug 496521 has been marked as a duplicate of this bug. ***
*** Bug 486452 has been marked as a duplicate of this bug. ***
So, only GNome 2.18 is affected. Can you please upgrade to Gnome 2.20 and retry to reproduce the crash?
Isn't this just another case of Bug 440988?
Thanks TOm, it is. I did not see that with my first search because the detailed search does not include closed reporty by default *cough cough* <alex_> My guess is that people with this problem ran an old glib + nautilus and then just updated glib Soo, I believe a logout+login is a workaround for this crash. But upgrading to Gnome 2.20 seems to solve this issue for everybody. Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 440988 ***