GNOME Bugzilla – Bug 497310
crash in Open Folder: Opening an ODT document
Last modified: 2007-11-16 13:44:42 UTC
Version: 2.18.3 What were you doing when the application crashed? Opening an ODT document 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: gartoon Memory status: size: 76513280 vsize: 76513280 resident: 25698304 share: 15310848 rss: 25698304 rss_rlim: 4294967295 CPU usage: start_time: 1195199143 rtime: 776 utime: 720 stime: 56 cutime:0 cstime: 1 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 0xb6dc96b0 (LWP 8007)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178073
Thread 1 (Thread 0xb6dc96b0 (LWP 8007))
----------- .xsession-errors --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x2a0001d (Manual MER); these messages lack timestamps and therefore suck. Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x280001d (Manual MER); these messages lack timestamps and therefore suck. ** 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 ***