GNOME Bugzilla – Bug 571276
crash in Evolution Mail and Calendar:
Last modified: 2009-02-11 11:07:42 UTC
What were you doing when the application crashed? Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.12-170.2.5.fc10.x86_64 #1 SMP Wed Jan 21 01:33:24 EST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 760926208 vsize: 760926208 resident: 52097024 share: 21823488 rss: 52097024 rss_rlim: 18446744073709551615 CPU usage: start_time: 1234335846 rtime: 1349 utime: 1155 stime: 194 cutime:1 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fa3177677e0 (LWP 3544)] [New Thread 0x7fa2fb303950 (LWP 4558)] [New Thread 0x7fa304dfa950 (LWP 3589)] 0x000000333c60ec2f in __libc_waitpid (pid=4565, stat_loc=0x7fff1f7b43f0, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 212451
Thread 2 (Thread 0x7fa2fb303950 (LWP 4558))
----------- .xsession-errors (861 sec old) --------------------- (evolution:3544): camel-imap-provider-WARNING **: Unable to load summary no such table: Drafts (evolution:3544): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:3544): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:3544): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed (evolution:3544): camel-WARNING **: Trying to check junk data is OBJECT 'CamelObject' (evolution:3544): camel-CRITICAL **: camel_object_is: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed (evolution:3544): camel-CRITICAL **: camel_object_unref: assertion `CAMEL_IS_OBJECT(o)' failed --------------------------------------------------
This has been fixed today and the fix will be included in version 2.24.5. *** This bug has been marked as a duplicate of 569700 ***