GNOME Bugzilla – Bug 510829
crash in Open Folder:
Last modified: 2008-01-21 14:20:56 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.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: Permissive Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 89100288 vsize: 89100288 resident: 21884928 share: 17838080 rss: 21884928 rss_rlim: 4294967295 CPU usage: start_time: 1200845599 rtime: 55 utime: 41 stime: 14 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 -1208731936 (LWP 31527)] [New Thread -1221321840 (LWP 31530)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 186087
Thread 1 (Thread -1208731936 (LWP 31527))
----------- .xsession-errors (8 sec old) --------------------- warning: .dynamic section for "/usr/lib/libgstinterfaces-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libgstaudio-0.10.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations (bug-buddy:31482): GLib-GObject-WARNING **: invalid uninstantiatable type `void' in cast to `GObject' (bug-buddy:31482): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:31482): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:31482): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 439977 ***