GNOME Bugzilla – Bug 507410
crash in File Browser: no se
Last modified: 2008-01-07 13:25:52 UTC
Version: 2.18.1 What were you doing when the application crashed? no se Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 550465536 vsize: 550465536 resident: 96145408 share: 21004288 rss: 96145408 rss_rlim: 18446744073709551615 CPU usage: start_time: 1199460374 rtime: 7132 utime: 6134 stime: 998 cutime:125 cstime: 59 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496397360 (LWP 3113)] (no debugging symbols found) 0x000000318480d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 184122
Thread 1 (Thread 46912496397360 (LWP 3113))
----------- .xsession-errors (9 sec old) --------------------- (nautilus:3113): Gtk-CRITICAL **: gtk_tree_model_sort_iter_next: assertion `tree_model_sort->stamp == iter->stamp' failed (nautilus:3113): Gtk-CRITICAL **: file gtktreeview.c: line 6054 (do_validate_rows): assertion `gtk_tree_model_iter_next (tree_view->priv->model, &iter)' 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. closing Advertencia del gestor de ventanas: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x360005b (OpenOffice) Advertencia del gestor de ventanas: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) aborting... --------------------------------------------------
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 356672 ***