GNOME Bugzilla – Bug 504649
crash in Tasks:
Last modified: 2007-12-20 16:01:34 UTC
Version: 2.10 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.8-34.fc7 #1 SMP Thu Nov 22 23:05:33 EST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70000001 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Mac4Lin_GTK_v0.3 Icon Theme: Leopard_Icons_v0.3 Memory status: size: 158015488 vsize: 158015488 resident: 41574400 share: 34484224 rss: 41574400 rss_rlim: 4294967295 CPU usage: start_time: 1198153779 rtime: 115 utime: 98 stime: 17 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (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 -1209100576 (LWP 26737)] [New Thread -1241646192 (LWP 26840)] [New Thread -1254098032 (LWP 26757)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 182427
Thread 1 (Thread -1209100576 (LWP 26737))
----------- .xsession-errors (285022 sec old) --------------------- (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (avant-window-navigator:6911): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed ...Too much output, ignoring rest... --------------------------------------------------
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 364700 ***