GNOME Bugzilla – Bug 552394
crash in File Browser:
Last modified: 2008-09-16 10:34:58 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Nuvola Icon Theme: Nuvola Memory status: size: 136306688 vsize: 136306688 resident: 66428928 share: 17063936 rss: 66428928 rss_rlim: 4294967295 CPU usage: start_time: 1221492904 rtime: 3608 utime: 3297 stime: 311 cutime:1480 cstime: 122 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ad5720 (LWP 3451)] [New Thread 0xb5208b90 (LWP 5726)] (no debugging symbols found) 0xb7f01424 in __kernel_vsyscall ()
+ Trace 206804
Thread 1 (Thread 0xb6ad5720 (LWP 3451))
----------- .xsession-errors (13 sec old) --------------------- (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***