GNOME Bugzilla – Bug 501013
crash in File Browser: hello, I don't know shou...
Last modified: 2007-12-02 19:20:05 UTC
Version: 2.18.3 What were you doing when the application crashed? hello, I don't know should I send you this message, but all the time I have place to send it when I try to see propertis of any file or directory from menu I don't know, my fault or no, it happends after upgrade gnome to v 2.18, with gtk and then downgrade gtk here you have details, maby it will be usefull Debian 4.0, 2.6.23, gnome from debian leny repository regards, mat Distribution: Debian 4.0 Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.23 #1 SMP Wed Oct 24 17:30:53 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Raleigh Icon Theme: crystalsvg Memory status: size: 74747904 vsize: 74747904 resident: 22839296 share: 15007744 rss: 22839296 rss_rlim: 4294967295 CPU usage: start_time: 1196598046 rtime: 299 utime: 277 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/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227192656 (LWP 3808)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 180410
Thread 1 (Thread -1227192656 (LWP 3808))
----------- .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 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 440988 ***