GNOME Bugzilla – Bug 570795
crash in Evolution Mail and Calendar: viewing emails
Last modified: 2009-02-06 15:55:49 UTC
What were you doing when the application crashed? viewing emails Distribution: Gentoo Base System release 2.0.0 Gnome Release: 2.24.3 2009-02-02 (Gentoo) BugBuddy Version: 2.24.2 System: Linux 2.6.25-gentoo-r9 #4 SMP PREEMPT Mon Jan 26 12:37:03 EST 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: KillBang Wow! Icon Theme: Paper Memory status: size: 375177216 vsize: 375177216 resident: 54927360 share: 22581248 rss: 54927360 rss_rlim: 18446744073709551615 CPU usage: start_time: 1233935205 rtime: 1981 utime: 1574 stime: 407 cutime:206 cstime: 66 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/evo/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb66236c0 (LWP 16485)] [New Thread 0xa31feb90 (LWP 20014)] [New Thread 0xa39ffb90 (LWP 19293)] [New Thread 0xb5b8db90 (LWP 16919)] [New Thread 0xa83feb90 (LWP 16914)] [New Thread 0xb3eacb90 (LWP 16873)] [New Thread 0xb36abb90 (LWP 16829)] 0xffffe424 in __kernel_vsyscall ()
+ Trace 212301
Thread 2 (Thread 0xa31feb90 (LWP 20014))
----------- .xsession-errors (333 sec old) --------------------- Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... Error - cannot end transaction. Rolling back... --------------------------------------------------
*** This bug has been marked as a duplicate of 569700 ***