GNOME Bugzilla – Bug 516512
crash in Open Folder:
Last modified: 2008-02-15 10:19:41 UTC
Version: 2.18.3 What were you doing when the application crashed? 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.24.2-1.rt1.3.fc7.ccrmart #1 SMP PREEMPT RT Tue Feb 12 18:18:11 EST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 118681600 vsize: 118681600 resident: 51191808 share: 33931264 rss: 51191808 rss_rlim: 4294967295 CPU usage: start_time: 1202952874 rtime: 1023 utime: 896 stime: 127 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 -1208682784 (LWP 7064)] (no debugging symbols found) 0xb7f8b410 in __kernel_vsyscall ()
+ Trace 189217
Thread 1 (Thread -1208682784 (LWP 7064))
----------- .xsession-errors (7 sec old) --------------------- ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name ** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2 specified for 0x4001305 (Choose a B). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x2 specified for 0x40013df (Warning). ** 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 459221 ***