GNOME Bugzilla – Bug 626794
crash in Evolution: Idle
Last modified: 2010-08-13 13:11:10 UTC
What were you doing when the application crashed? Idle Distribution: Debian squeeze/sid Gnome Release: 2.30.0 2010-04-26 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.34-1-686 #1 SMP Sun Jun 6 22:56:48 UTC 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome GTK+ Modules: gnomebreakpad Memory status: size: 258646016 vsize: 258646016 resident: 57069568 share: 25083904 rss: 57069568 rss_rlim: 18446744073709551615 CPU usage: start_time: 1281686061 rtime: 2097 utime: 1900 stime: 197 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 0xaa6fbb70 (LWP 3877)] [New Thread 0xac6ffb70 (LWP 3715)] [New Thread 0xab6fdb70 (LWP 3712)] [New Thread 0xad045b70 (LWP 3711)] [New Thread 0xb10fbb70 (LWP 3701)] [New Thread 0xb18fcb70 (LWP 3700)] [New Thread 0xb3cfeb70 (LWP 3696)] [New Thread 0xb44ffb70 (LWP 3695)] [New Thread 0xb4e95b70 (LWP 3694)] [New Thread 0xb56cdb70 (LWP 3693)] 0xb785f424 in __kernel_vsyscall ()
+ Trace 223218
Thread 3 (Thread 0xac6ffb70 (LWP 3715))
Inferior 1 [process 3691] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (10 sec old) --------------------- camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: database disk image is malformed camel-imap-provider-Message: Unable to load summary: database disk image is malformed --------------------------------------------------
Same as bug 622356 *** This bug has been marked as a duplicate of bug 573125 ***