GNOME Bugzilla – Bug 511374
crash in File Browser:
Last modified: 2008-01-23 10:32:31 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.23.1-21.fc7 #1 SMP Thu Nov 1 20:28:15 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Mac4Lin_GTK_Aqua_v0.3 Icon Theme: OSX Memory status: size: 426369024 vsize: 426369024 resident: 46678016 share: 27033600 rss: 46678016 rss_rlim: 18446744073709551615 CPU usage: start_time: 1201046173 rtime: 703 utime: 519 stime: 184 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496393760 (LWP 3170)] (no debugging symbols found) 0x0000003ab0c0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 186402
Thread 1 (Thread 46912496393760 (LWP 3170))
----------- .xsession-errors --------------------- fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub fixme:shell:DllCanUnloadNow stub ** (gnome-session:3054): WARNING **: Invalid borders specified for theme pixmap: /home/marquitux/.themes/Mac4Lin_GTK_Aqua_v0.3/gtk-2.0/Buttons/button-default.png, borders don't fit within the image (nautilus:3170): Gtk-CRITICAL **: gtk_tree_model_sort_real_unref_node: assertion `elt->ref_count > 0' failed ** ERROR **: file fm-tree-model.c: line 1531 (fm_tree_model_unref_node): assertion failed: (node->ref_count > 0) aborting... warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff017f0000 --------------------------------------------------
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 ***