GNOME Bugzilla – Bug 435962
crash in CD/DVD Creator: click on folder in brows...
Last modified: 2007-05-07 20:23:44 UTC
What were you doing when the application crashed? click on folder in browser 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.20-1.2948.fc6 #1 SMP Fri Apr 27 19:48:40 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 118542336 vsize: 0 resident: 118542336 share: 0 rss: 31653888 rss_rlim: 0 CPU usage: start_time: 1178299114 rtime: 0 utime: 773 stime: 0 cutime:694 cstime: 0 timeout: 79 it_real_value: 0 frequency: 29 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 -1208998192 (LWP 3420)] (no debugging symbols found) 0x00f05402 in __kernel_vsyscall ()
+ Trace 132436
Thread 1 (Thread -1208998192 (LWP 3420))
----------- .xsession-errors --------------------- (nautilus:3420): GLib-GObject-CRITICAL **: g_object_unref: assertion `object->ref_count > 0' failed (nautilus:3420): GLib-CRITICAL **: g_node_traverse: assertion `root != NULL' failed (nautilus:3420): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:3420): Gtk-CRITICAL **: update_node: assertion `node != NULL' failed report junk?? No more difficulties with your health just use our preparations ** (nautilus:3420): CRITICAL **: nautilus_window_info_get_window_type: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (nautilus:3420): CRITICAL **: nautilus_window_info_get_ui_manager: assertion `NAUTILUS_IS_WINDOW_INFO (window)' failed ** (bug-buddy:12230): WARNING **: Symbol für Ordner öffnen konnte nicht geladen werden --------------------------------------------------
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 ***