GNOME Bugzilla – Bug 573743
crash in File Browser: Nautilus scripts
Last modified: 2009-03-02 13:21:11 UTC
Version: 2.20.0 What were you doing when the application crashed? Nautilus scripts Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Nov 8 19:00:26 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Mac4Lin_GTK_v1.0_RC Icon Theme: Mac4Lin_Icons_v1.0_RC Memory status: size: 128671744 vsize: 128671744 resident: 33202176 share: 17653760 rss: 33202176 rss_rlim: 4294967295 CPU usage: start_time: 1235901116 rtime: 3466 utime: 2696 stime: 770 cutime:150 cstime: 22 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6a609a0 (LWP 5331)] 0xb7f65424 in __kernel_vsyscall ()
+ Trace 213056
Thread 1 (Thread 0xb6a609a0 (LWP 5331))
----------- .xsession-errors (10 sec old) --------------------- (nautilus:5331): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NautilusPlacesSidebar' (nautilus:5331): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed (nautilus:5331): Gtk-CRITICAL **: gtk_list_store_clear: assertion `GTK_IS_LIST_STORE (list_store)' failed ** (nautilus:5331): CRITICAL **: nautilus_window_info_get_current_location: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed (nautilus:5331): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:5331): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:5331): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (nautilus:5331): Gtk-CRITICAL **: gtk_tree_model_filter_convert_child_iter_to_iter: assertion `child_path != NULL' failed --------------------------------------------------
This particular bug has already been reported into our bug tracking system. *** This bug has been marked as a duplicate of 356497 ***