GNOME Bugzilla – Bug 504623
crash in Home Folder: I just closed a nautilus...
Last modified: 2007-12-20 11:35:06 UTC
What were you doing when the application crashed? I just closed a nautilus window after closing a pdf document. 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 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: 162582528 vsize: 162582528 resident: 45031424 share: 22794240 rss: 45031424 rss_rlim: 4294967295 CPU usage: start_time: 1198131910 rtime: 3083 utime: 2759 stime: 324 cutime:85 cstime: 33 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 -1209043232 (LWP 3076)] [New Thread -1320363120 (LWP 4372)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182413
Thread 1 (Thread -1209043232 (LWP 3076))
----------- .xsession-errors --------------------- ** ERROR **: file fm-tree-model.c: line 1527 (fm_tree_model_unref_node): assertion failed: (parent->dummy_child_ref_count > 0) aborting... warning: .dynamic section for "/usr/lib/libeel-2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgnome-desktop-2.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgnome-window-settings.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 ***