GNOME Bugzilla – Bug 497165
crash in File Browser: view the property of a f...
Last modified: 2007-11-16 13:43:27 UTC
Version: 2.18.3 What were you doing when the application crashed? view the property of a file 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: Nuvola Icon Theme: Vista-Inspirate_1.0 Memory status: size: 78278656 vsize: 78278656 resident: 27680768 share: 15470592 rss: 27680768 rss_rlim: 4294967295 CPU usage: start_time: 1195117008 rtime: 1492 utime: 1359 stime: 133 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 0xb6dca6b0 (LWP 4042)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 177963
Thread 1 (Thread 0xb6dca6b0 (LWP 4042))
----------- .xsession-errors --------------------- Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x285fd4b (OpenOffice) Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. JACK tmpdir identified as [/dev/shm] /usr/bin/gnome-open ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (gnome-panel:20990): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -15 and height 25 ** 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 ***