GNOME Bugzilla – Bug 581996
crash in Evolution Mail and Calendar: Evolution crashes each t...
Last modified: 2009-05-09 16:16:20 UTC
What were you doing when the application crashed? Evolution crashes each time I try to start it. It also happens with a fresh user account. I'm running debian testing with few desktop-packages from unstable. Distribution: Debian squeeze/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.24.2 System: Linux 2.6.26-2-686-bigmem #1 SMP Thu Mar 26 02:03:34 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist Memory status: size: 57028608 vsize: 57028608 resident: 16084992 share: 13422592 rss: 16084992 rss_rlim: 18446744073709551615 CPU usage: start_time: 1241884649 rtime: 18 utime: 16 stime: 2 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 0xb5138770 (LWP 5594)] 0xb7f26424 in __kernel_vsyscall ()
+ Trace 215277
Thread 1 (Thread 0xb5138770 (LWP 5594))
----------- .xsession-errors --------------------- (evolution:4018): camel-WARNING **: camel_type_register: 'MailSession' has smaller class size than parent 'CamelSession' (evolution:4018): camel-CRITICAL **: camel_object_cast: assertion `o != NULL' failed (evolution:5545): camel-WARNING **: camel_type_register: 'MailSession' has smaller class size than parent 'CamelSession' (evolution:5545): camel-CRITICAL **: camel_object_cast: assertion `o != NULL' failed warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4 (evolution:5594): camel-WARNING **: camel_type_register: 'MailSession' has smaller class size than parent 'CamelSession' (evolution:5594): camel-CRITICAL **: camel_object_cast: assertion `o != NULL' failed warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4 --------------------------------------------------
> I'm running debian testing with few desktop-packages from unstable. And I think this crash only happens because mixing up 2.24 and 2.22 in Debian. :) Same issue as bug 580402. *** This bug has been marked as a duplicate of 580402 ***