GNOME Bugzilla – Bug 497336
crash in Home Folder: Hello, I wanted to have...
Last modified: 2007-11-16 13:44:43 UTC
What were you doing when the application crashed? Hello, I wanted to have a look at the attributes of a file. This mistake appears often but not always. Greetings Burghardt Scholle 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: Colin Harrison X Vendor Release: 60900028 Selinux: No Accessibility: Disabled GTK+ Theme: Default Icon Theme: gnome Memory status: size: 78450688 vsize: 78450688 resident: 22396928 share: 13963264 rss: 22396928 rss_rlim: 4294967295 CPU usage: start_time: 1195208921 rtime: 222 utime: 200 stime: 22 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6d6a6b0 (LWP 3937)] (no debugging symbols found) 0xb75c1bf1 in waitpid () from /lib/libpthread.so.0
+ Trace 178093
Thread 1 (Thread 0xb6d6a6b0 (LWP 3937))
----------- .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... --------------------------------------------------
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 ***