GNOME Bugzilla – Bug 578156
crash in Image Viewer: fechando
Last modified: 2009-04-06 19:31:30 UTC
Version: 2.22.3 What were you doing when the application crashed? fechando Distribution: Debian 4.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 40955904 vsize: 40955904 resident: 16703488 share: 10989568 rss: 16703488 rss_rlim: 4294967295 CPU usage: start_time: 1239037455 rtime: 32 utime: 24 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/eog' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6a75b40 (LWP 15441)] [New Thread 0xb68adb90 (LWP 15442)] (no debugging symbols found) 0xb7f95424 in __kernel_vsyscall ()
+ Trace 214228
Thread 1 (Thread 0xb6a75b40 (LWP 15441))
----------- .xsession-errors (10 sec old) --------------------- (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_hide: assertion `GTK_IS_WIDGET (widget)' failed (firefox-bin:13914): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed --------------------------------------------------
Most likely a dupe of #523463. Marking as duplicate. Fixed as of GLib 2.18. 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 523463 ***