GNOME Bugzilla – Bug 376093
crash in CD/DVD Creator: Opening Nautilus. Double...
Last modified: 2006-11-17 16:26:39 UTC
What were you doing when the application crashed? Opening Nautilus. Double clicked on "dale's Home" on desktop. Opened a sub-folder in my home. Opened a sub-sub-folder in my home. Got this lovely message. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.18-1.2849.fc6 #1 SMP Fri Nov 10 12:36:14 EST 2006 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled ----------- .xsession-errors (71469 sec old) --------------------- (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed (nautilus:3010): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed ...Too much output, ignoring rest... -------------------------------------------------- Memory status: size: 490242048 vsize: 0 resident: 490242048 share: 0 rss: 375209984 rss_rlim: 0 CPU usage: start_time: 1163511160 rtime: 0 utime: 77344 stime: 0 cutime:71513 cstime: 0 timeout: 5831 it_real_value: 0 frequency: 478 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 -1209087232 (LWP 3010)] (no debugging symbols found) 0x0026c402 in __kernel_vsyscall ()
+ Trace 87047
Thread 1 (Thread -1209087232 (LWP 3010))
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 374002 ***