GNOME Bugzilla – Bug 586713
crash in Evolution Mail and Calendar: I created a new message,...
Last modified: 2009-06-23 13:29:40 UTC
What were you doing when the application crashed? I created a new message, escaped it (Key ESC) and switch the selection of another account / Inbox Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.24.3 2009-05-17 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.28-gentoo-r5 #1 SMP Mon Apr 27 08:15:24 CEST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 130953216 vsize: 130953216 resident: 41168896 share: 22650880 rss: 41168896 rss_rlim: 18446744073709551615 CPU usage: start_time: 1245737871 rtime: 1578 utime: 1479 stime: 99 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb641f700 (LWP 10852)] [New Thread 0xb12fdb90 (LWP 10945)] [New Thread 0xb59d5b90 (LWP 10938)] [New Thread 0xb2c55b90 (LWP 10875)] [New Thread 0xb51afb90 (LWP 10874)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 216148
Thread 1 (Thread 0xb641f700 (LWP 10852))
----------- .xsession-errors (47 sec old) --------------------- (firefox-bin:9975): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Error: FormFieldButton::setState called on a readOnly field (firefox-bin:9975): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:9975): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:9975): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (firefox-bin:9975): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (evolution:10852): gtkhtml-editor-WARNING **: en-US: No such language (evolution:10852): GLib-GObject-WARNING **: invalid unclassed pointer in cast to `GtkWidget' --------------------------------------------------
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 535516 ***