GNOME Bugzilla – Bug 518771
crash in Open Folder: Just logged in Fedora.
Last modified: 2008-02-26 19:59:05 UTC
Version: 2.18.3 What were you doing when the application crashed? Just logged in Fedora. 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.21-6.fc7xen #1 SMP Mon Nov 19 07:14:57 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 467763200 vsize: 467763200 resident: 25944064 share: 19345408 rss: 25944064 rss_rlim: 18446744073709551615 CPU usage: start_time: 1204000314 rtime: 28 utime: 23 stime: 5 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 46912496454704 (LWP 2640)] (no debugging symbols found) 0x0000003a62c0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 190466
Thread 1 (Thread 46912496454704 (LWP 2640))
----------- .xsession-errors --------------------- (bug-buddy:2583): GLib-GObject-WARNING **: invalid uninstantiatable type `motion-notify-event' in cast to `GObject' (bug-buddy:2583): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:2583): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:2583): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed ** (nm-applet:2528): WARNING **: <WARN> nma_dbus_init(): org.freedesktop.DBus.Error.FileNotFound raised: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory --------------------------------------------------
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 499229 ***