GNOME Bugzilla – Bug 324539
EDS crash takes down Contacts, Calendar and Tasks
Last modified: 2008-11-30 21:30:29 UTC
When typing an address in the "To" or "CC" fields, the evolution-data-server will sometimes crash. When it does, it takes down the Task Server, Calendar server and Contacts server. I have autocompletion turned on for the Personal and a corporate LDAP address book, but the autocompletion sometimes is not able to suggest matches, especially if I am typing an address for which there is no match. The crash most commonly occurs after the VPN connection to my company is dropped and restarted (the corporate LDAP address book is only accessable when the VPN is up). This problem occured in Evolution 1.4.x and it continues in Evolution 2.4.x as well. I asked for advice on the evolution mailing list, and was told to enter a problem report with a stack trace of EDS. I attached to the process with gdb and ran into several SIGPIPE signals, each of which was continuable (stack traces of those are also available, but omitted here). The signal that I could not continue was SIGABRT. Here is the trace: (gdb) c Program received signal SIGABRT, Aborted. 0xffffe410 in ?? () (gdb) where
+ Trace 64706
After I typed "continue" I received the following 4 dialog boxes in turn: "The Evolution tasks have quit unexpectedly." "Your tasks will not be available until Evolution is restarted." "The Evolution calendar has quit unexpectedly." "Your calendars will not be available until Evolution is restarted." "The evolution addressbook has quit unexpectedly." "Your contacts for ldap://ldap.company.com:389/o=company.com??sub will not be available until Evolution is restarted." "The Evolution addressbook has quit unexpectedly." "Your contacts for file:///home/user/.evolution/addressbook/local/system will not be available until Evolution is restarted." At this point, I run evolution --force-shutdown and then restart evolution. System: Ubuntu Breeze Badger Uname: Linux linux 2.6.12-10-386 #1 Fri Nov 18 11:51:02 UTC 2005 i686 GNU/Linux
Hi jnmnus, thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
I've seen this bug in evolution for a year or two and has preventing me from using it, I'd be very interested in getting this fixed. It doesn't happen all the time, but next time it does I'll get a stack trace There isn't a crash, it just hangs indefinitely, I figured it would be fixed in the latest version in fedora 10, but this hasn't happened.