GNOME Bugzilla – Bug 581287
crash in Evolution Mail and Calendar: Evolution crashed while ...
Last modified: 2009-05-04 12:17:33 UTC
What were you doing when the application crashed? Evolution crashed while opening the inbox Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.24.2 System: Linux 2.6.29-1-686 #1 SMP Fri Apr 17 14:35:16 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10601000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Tango Memory status: size: 208834560 vsize: 208834560 resident: 130875392 share: 8986624 rss: 130875392 rss_rlim: 18446744073709551615 CPU usage: start_time: 1241430434 rtime: 680 utime: 592 stime: 88 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 0xb5241770 (LWP 6057)] [New Thread 0xb4e20b90 (LWP 6066)] 0xb8057424 in __kernel_vsyscall ()
+ Trace 215087
Thread 1 (Thread 0xb5241770 (LWP 6057))
----------- .xsession-errors (27 sec old) --------------------- camel-imap-provider-Message: Unable to load summary: no such table: indigenous/jabiluka camel-imap-provider-Message: Unable to load summary: no such table: pol camel-imap-provider-Message: Unable to load summary: no such table: sib (evolution:9946): camel-exchange-provider-WARNING **: Unable to load Exchage summary for folder personal/Posteingang/Information Centres: no such table: personal/Posteingang/Information Centres (evolution:9946): camel-exchange-provider-WARNING **: Unable to load Exchage summary for folder personal/Posteingang/Information Centres/RITC: no such table: personal/Posteingang/Information Centres/R (evolution:9946): camel-exchange-provider-WARNING **: Unable to load Exchage summary for folder personal/Posteingang/UPR: no such table: personal/Posteingang/UPR --------------------------------------------------
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 522277 ***