GNOME Bugzilla – Bug 508281
crash in Open Folder: installing labview
Last modified: 2008-01-10 01:36:08 UTC
Version: 2.18.3 What were you doing when the application crashed? installing labview Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 96452608 vsize: 96452608 resident: 40017920 share: 25882624 rss: 40017920 rss_rlim: 4294967295 CPU usage: start_time: 1199880110 rtime: 755 utime: 636 stime: 119 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 -1208219936 (LWP 2740)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 184661
Thread 1 (Thread -1208219936 (LWP 2740))
----------- .xsession-errors (8 sec old) --------------------- SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2618 ** (gnome-session:2618): WARNING **: Host name lookup failure on localhost. --- Hash table keys for warning below: --> file:///home/giseli (nautilus:2979): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) ** (nautilus:2740): WARNING **: destroyed file has call_when_ready pending ** (nautilus:2740): WARNING **: destroyed file has call_when_ready pending ** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->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 ***