GNOME Bugzilla – Bug 573822
crash in Evolution Mail and Calendar: clicked web link in emai...
Last modified: 2009-03-03 03:42:50 UTC
What were you doing when the application crashed? clicked web link in email; then clicked calendar. Distribution: Debian 5.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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 41095168 vsize: 41095168 resident: 10018816 share: 8388608 rss: 10018816 rss_rlim: 4294967295 CPU usage: start_time: 1236028193 rtime: 12 utime: 8 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/lib/bug-buddy/evolution-exchange-storage' [Thread debugging using libthread_db enabled] [New Thread 0xb63bb750 (LWP 13524)] [New Thread 0xb60e1b90 (LWP 13528)] 0xb7f05424 in __kernel_vsyscall ()
+ Trace 213083
Thread 1 (Thread 0xb63bb750 (LWP 13524))
----------- .xsession-errors (1019623 sec old) --------------------- (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed (xcdroast:5388): Gtk-CRITICAL **: gtk_widget_event: assertion `WIDGET_REALIZED_FOR_EVENT (widget, event)' failed ...Too much output, ignoring rest... --------------------------------------------------
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 513113 ***