GNOME Bugzilla – Bug 491001
crash in Open Folder: Logging in.
Last modified: 2007-10-29 02:09:30 UTC
Version: 2.18.3 What were you doing when the application crashed? Logging in. Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21 #1 SMP Fri Oct 26 08:58:59 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Enabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 42991616 vsize: 42991616 resident: 11714560 share: 9031680 rss: 11714560 rss_rlim: 4294967295 CPU usage: start_time: 1193565298 rtime: 44 utime: 21 stime: 23 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 -1208613152 (LWP 3211)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 173388
Thread 1 (Thread -1208613152 (LWP 3211))
----------- .xsession-errors (34 sec old) --------------------- (bug-buddy:2951): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:2951): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:2951): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:2951): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed GTK Accessibility Module initialized Bonobo accessibility support initialized seahorse nautilus module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 442829 ***