GNOME Bugzilla – Bug 542290
crash in File Browser:
Last modified: 2008-07-10 02:07:39 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: Nuvola Icon Theme: Nuvola Memory status: size: 86974464 vsize: 86974464 resident: 23535616 share: 14102528 rss: 23535616 rss_rlim: 4294967295 CPU usage: start_time: 1215622338 rtime: 5665 utime: 5185 stime: 480 cutime:7 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6a80720 (LWP 2913)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 202445
Thread 1 (Thread 0xb6a80720 (LWP 2913))
----------- .xsession-errors --------------------- (nautilus:2913): Gtk-CRITICAL **: gtk_tree_view_get_selection: assertion `GTK_IS_TREE_VIEW (tree_view)' failed (nautilus:2913): Gtk-CRITICAL **: gtk_list_store_clear: assertion `GTK_IS_LIST_STORE (list_store)' failed ** (nautilus:2913): CRITICAL **: nautilus_window_info_get_current_location: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed (nautilus:2913): Gtk-CRITICAL **: gtk_list_store_append: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:2913): Gtk-CRITICAL **: gtk_list_store_set_valist: assertion `GTK_IS_LIST_STORE (list_store)' failed (nautilus:2913): Gtk-CRITICAL **: gtk_list_store_get_path: assertion `iter->stamp == GTK_LIST_STORE (tree_model)->stamp' failed (nautilus:2913): Gtk-CRITICAL **: gtk_tree_model_filter_convert_child_iter_to_iter: assertion `child_path != NULL' failed Cannot access memory at address 0x0 Cannot access memory at address 0x0 --------------------------------------------------
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 ***