GNOME Bugzilla – Bug 470122
crash in File Browser: Closing time (again)
Last modified: 2007-09-11 15:40:16 UTC
Version: 2.18.3 What were you doing when the application crashed? Closing time (again) 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.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 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: 93601792 vsize: 93601792 resident: 22065152 share: 10203136 rss: 22065152 rss_rlim: 4294967295 CPU usage: start_time: 1188026768 rtime: 1219 utime: 1059 stime: 160 cutime:0 cstime: 0 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 -1208142112 (LWP 2421)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 157766
Thread 1 (Thread -1208142112 (LWP 2421))
----------- .xsession-errors (16 sec old) --------------------- 02:28:24 : --> tcl-devel - 1:8.4.13-16.fc7.i386 02:28:24 : --> tk-devel - 1:8.4.13-5.fc7.i386 02:28:24 : Dependency Installed: 02:28:24 : --> libX11-devel - 1.0.3-8.fc7.i386 02:28:24 : --> libXau-devel - 1.0.3-1.fc7.i386 02:28:24 : --> libXdmcp-devel - 1.0.2-2.fc7.i386 02:28:24 : --> mesa-libGL-devel - 6.5.2-13.fc7.i386 02:28:24 : --> xorg-x11-proto-devel - 7.2-9.fc7.i386 Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) aborting... --------------------------------------------------
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 449151 ***