GNOME Bugzilla – Bug 577189
crash in Evolution Mail and Calendar: I simply tried to close ...
Last modified: 2009-04-01 17:56:11 UTC
What were you doing when the application crashed? I simply tried to close the application. Distribution: Debian squeeze/sid Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.24.2 System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 364408832 vsize: 364408832 resident: 59023360 share: 22482944 rss: 59023360 rss_rlim: 18446744073709551615 CPU usage: start_time: 1238336573 rtime: 5299 utime: 4589 stime: 710 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb51b0770 (LWP 21993)] [New Thread 0xa56f7b90 (LWP 22242)] [New Thread 0xa4ef6b90 (LWP 22233)] [New Thread 0xb408bb90 (LWP 22001)] [New Thread 0xb48bab90 (LWP 22000)] 0xb7eee424 in __kernel_vsyscall ()
+ Trace 213967
Thread 2 (Thread 0xa56f7b90 (LWP 22242))
----------- .xsession-errors --------------------- (evolution:21993): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/spam/misc (evolution:21993): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/spam/spamassassin (evolution:21993): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/spam/virus (evolution:21993): camel-imap-provider-WARNING **: Unable to load summary no such table: INBOX/test warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4 --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I hope, the next backtraces are more useful. Evolution crashes for me in combination with sqlite3 3.6.10 pretty often. It is not possible to determine exactly, when it crashes, but it happens quite often during exit. I attach two stacktrace for these crashes: evolution.log (by bug-buddy) and gdb.txt (by running gdb). When Evolution crashes, it will segfault at every startup too, making it impossible to use it. I can then just delete .evolution. The backtrace found in evolution_start.log was made by bug-buddy during startup of evolution. If I can provide more information, please don't hesitate to tell me! There are several reports about this issue at the Debian BTS: http://bugs.debian.org/519206 http://bugs.debian.org/519428 http://bugs.debian.org/521608 http://bugs.debian.org/521752 PS: This could be a duplicate of (or at least be related to) #575084.
...still needs a better stacktrace here -> NEEDINFO.
Created attachment 131695 [details] backtrace (crash during exit by bug-buddy) This one was made by bug-buddy. Crash happened during Exit (I simply used to set some ordering direction for some folders and marked some messages as "read").
Created attachment 131696 [details] backtrace (by gdb, again crash during exit) Backtrace by gdb. Started evolution, set some ordering, marked some messages as "read" and close evolution - at the 3. or 4. time it crashed on exit).
Created attachment 131697 [details] backrtace (by bug-buddy, always crashing on startup after the crash on exit) This is a backtrace made by bug-buddy during startup. As I wrote, after crashing on exit, evolution crashes on startup too (BTW independent from the component).
Hope, these backtraces help. Reopening. If you need more information, please tell me.
As far as I can say, this is a duplicate of #575084. I rebuilt evolution-data-server with sqlite3 3.6 and the crashes seem to be gone. *** This bug has been marked as a duplicate of 575084 ***