GNOME Bugzilla – Bug 508949
crash in File Browser:
Last modified: 2008-01-13 11:58:42 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.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: Mist Icon Theme: Mist Memory status: size: 84983808 vsize: 84983808 resident: 26247168 share: 16097280 rss: 26247168 rss_rlim: 4294967295 CPU usage: start_time: 1200145732 rtime: 618 utime: 564 stime: 54 cutime:122 cstime: 9 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 0xb6c8a6b0 (LWP 3556)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185043
Thread 1 (Thread 0xb6c8a6b0 (LWP 3556))
----------- .xsession-errors --------------------- (nautilus:3556): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `NautilusPlacesSidebar' (nautilus:3556): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed (nautilus:3556): Gtk-CRITICAL **: gtk_list_store_clear: assertion `GTK_IS_LIST_STORE (list_store)' failed ** (nautilus:3556): CRITICAL **: nautilus_window_info_get_current_location: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed (nautilus:3556): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:3556): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:3556): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (nautilus:3556): Gtk-CRITICAL **: gtk_tree_model_filter_convert_child_iter_to_iter: assertion `child_path != NULL' failed --------------------------------------------------
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 355018 ***