GNOME Bugzilla – Bug 559090
crash in Computer: I was unmounting an USB ...
Last modified: 2008-11-03 20:02:47 UTC
Version: 2.20.0 What were you doing when the application crashed? I was unmounting an USB storage device. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Neu Memory status: size: 87486464 vsize: 87486464 resident: 36499456 share: 17432576 rss: 36499456 rss_rlim: 4294967295 CPU usage: start_time: 1225708205 rtime: 7399 utime: 6954 stime: 445 cutime:3 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6a76710 (LWP 3424)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 209155
Thread 1 (Thread 0xb6a76710 (LWP 3424))
----------- .xsession-errors (12 sec old) --------------------- (nautilus:3424): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NautilusPlacesSidebar' (nautilus:3424): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed (nautilus:3424): Gtk-CRITICAL **: gtk_list_store_clear: assertion `GTK_IS_LIST_STORE (list_store)' failed ** (nautilus:3424): CRITICAL **: nautilus_window_info_get_current_location: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed (nautilus:3424): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:3424): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:3424): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (nautilus:3424): Gtk-CRITICAL **: gtk_tree_model_filter_convert_child_iter_to_iter: assertion `child_path != NULL' failed --------------------------------------------------
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 356497 ***