GNOME Bugzilla – Bug 599207
crash in Home Folder:
Last modified: 2009-10-21 15:59:13 UTC
What were you doing when the application crashed? Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.3 2009-07-07 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.30.8-64.fc11.i586 #1 SMP Fri Sep 25 04:30:19 EDT 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10603901 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: eGTK_0.11 Icon Theme: erectus-blue GTK+ Modules: canberra-gtk-module, globalmenu-gnome, pk-gtk-module, gnomebreakpad Memory status: size: 197935104 vsize: 197935104 resident: 32120832 share: 21127168 rss: 32120832 rss_rlim: 18446744073709551615 CPU usage: start_time: 1256137375 rtime: 853 utime: 748 stime: 105 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb08feb70 (LWP 2392)] 0x00f01422 in __kernel_vsyscall ()
+ Trace 218474
Thread 1 (Thread 0xb7fa9760 (LWP 2154))
---- Critical and fatal warnings logged during execution ---- ** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed ** GLib-GObject **: g_object_ref: assertion `object->ref_count > 0' failed ----------- .xsession-errors (9 sec old) --------------------- warning: .dynamic section for "/usr/lib/libgstvideo-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libnspr4.so" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/lib/libgpg-error.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libcroco-0.6.so.3" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations --------------------------------------------------
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 bug 579627 ***