GNOME Bugzilla – Bug 470385
crash in Computer:
Last modified: 2007-09-11 14:56: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-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-41.fc7 #1 SMP Fri Jul 27 18:21:43 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 458485760 vsize: 458485760 resident: 24371200 share: 16752640 rss: 24371200 rss_rlim: 18446744073709551615 CPU usage: start_time: 1188120405 rtime: 30 utime: 24 stime: 6 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 "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496434224 (LWP 27008)] (no debugging symbols found) 0x0000003ce720d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 157969
Thread 1 (Thread 46912496434224 (LWP 27008))
----------- .xsession-errors --------------------- seahorse nautilus module initialized (nautilus:26947): GLib-GObject-WARNING **: gsignal.c:2133: signal id `266' is invalid for instance `0xb5ee30' (nautilus:26947): GLib-GObject-WARNING **: gsignal.c:2133: signal id `266' is invalid for instance `0xb5c180' (bug-buddy:26992): GLib-GObject-WARNING **: invalid uninstantiatable type `key-press-event' in cast to `GObject' (bug-buddy:26992): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:26992): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:26992): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing nautilus-open-terminal extension seahorse nautilus module 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 441944 ***