GNOME Bugzilla – Bug 483557
crash in Computer:
Last modified: 2007-10-05 14:28:32 UTC
Version: 2.16.2 What were you doing when the application crashed? Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.22.5-49.fc6 #1 SMP Thu Aug 30 14:25:46 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 111579136 vsize: 0 resident: 111579136 share: 0 rss: 38903808 rss_rlim: 0 CPU usage: start_time: 1191547357 rtime: 0 utime: 8087 stime: 0 cutime:7461 cstime: 0 timeout: 626 it_real_value: 0 frequency: 62 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 -1208322352 (LWP 7213)] [New Thread -1283462256 (LWP 7775)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 167857
Thread 1 (Thread -1208322352 (LWP 7213))
----------- .xsession-errors --------------------- (nautilus:7213): GLib-CRITICAL **: g_node_traverse: assertion `root != NULL' failed (nautilus:7213): GLib-CRITICAL **: g_node_traverse: assertion `root != NULL' failed (nautilus:7213): Gtk-CRITICAL **: gtk_ui_manager_remove_action_group: assertion `GTK_IS_ACTION_GROUP (action_group)' failed (nautilus:7213): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:7213): Gtk-CRITICAL **: update_node: assertion `node != NULL' failed ** (nautilus:7213): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:7213): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (bug-buddy:7779): WARNING **: Couldn't load icon for Open Folder --------------------------------------------------
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 374002 ***