GNOME Bugzilla – Bug 551498
crash in Open Folder:
Last modified: 2008-09-09 12:15:27 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 83947520 vsize: 83947520 resident: 32088064 share: 16113664 rss: 32088064 rss_rlim: 4294967295 CPU usage: start_time: 1220991411 rtime: 1107 utime: 1021 stime: 86 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b23720 (LWP 3004)] [New Thread 0xb5ae4b90 (LWP 3606)] (no debugging symbols found) 0xb7f48424 in __kernel_vsyscall ()
+ Trace 206539
Thread 1 (Thread 0xb6b23720 (LWP 3004))
----------- .xsession-errors --------------------- (nautilus:3004): Gtk-CRITICAL **: file /tmp/buildd/gtk+2.0-2.12.10/gtk/gtktreeview.c: line 4882 (gtk_tree_view_bin_expose): assertion `has_parent' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. (nautilus:3004): Gtk-CRITICAL **: file /tmp/buildd/gtk+2.0-2.12.10/gtk/gtktreeview.c: line 4864 (gtk_tree_view_bin_expose): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. ** ** ERROR:(fm-tree-model.c:1527):fm_tree_model_unref_node: assertion failed: (parent->dummy_child_ref_count > 0) --------------------------------------------------
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 510468 ***