GNOME Bugzilla – Bug 571158
crash in Evolution Mail and Calendar: reviewing mail
Last modified: 2009-02-11 04:27:11 UTC
What were you doing when the application crashed? reviewing mail 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: 651685888 vsize: 651685888 resident: 46108672 share: 20746240 rss: 46108672 rss_rlim: 18446744073709551615 CPU usage: start_time: 1234264222 rtime: 295 utime: 248 stime: 47 cutime:2 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7f0c73db57e0 (LWP 12469)] [New Thread 0x7f0c60dfa950 (LWP 12503)] [New Thread 0x7f0c62bfd950 (LWP 12498)] 0x000000333c60ec2f in __libc_waitpid (pid=12612, stat_loc=0x7fff7be02c10, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 212423
Thread 3 (Thread 0x7f0c62bfd950 (LWP 12498))
----------- .xsession-errors (8 sec old) --------------------- (evolution:12469): camel-imap-provider-WARNING **: Unable to load summary no such table: Apple Mail To Do (evolution:12469): camel-imap-provider-WARNING **: Unable to load summary no such table: ByteCode/Meeting (evolution:12469): camel-imap-provider-WARNING **: Unable to load summary no such table: Collaboratori (evolution:12469): camel-imap-provider-WARNING **: Unable to load summary no such table: Contatti (evolution:12469): camel-imap-provider-WARNING **: Unable to load summary no such table: Drafts --------------------------------------------------
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 571152 ***