GNOME Bugzilla – Bug 491801
crash in Home Folder: i closed the aplication
Last modified: 2007-11-08 00:09:06 UTC
What were you doing when the application crashed? i closed the aplication Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 105852928 vsize: 105852928 resident: 38600704 share: 22581248 rss: 38600704 rss_rlim: 4294967295 CPU usage: start_time: 1193753248 rtime: 7812 utime: 7082 stime: 730 cutime:0 cstime: 19 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208678688 (LWP 5167)] [New Thread -1292731504 (LWP 7461)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 173975
Thread 1 (Thread -1208678688 (LWP 5167))
----------- .xsession-errors (39 sec old) --------------------- QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'make widget') QLayout "unnamed" added to IndexView "unnamed", which already has a layout (nautilus:5167): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed (nautilus:5167): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed (nautilus:5167): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (nautilus:5167): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed ** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) aborting... ICE default IO error handler doing an exit(), pid = 7331, errno = 0 --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 449151 ***