GNOME Bugzilla – Bug 604360
Crash in camel_exchange_utils_sync_count at camel-exchange-utils.c line 2323
Last modified: 2013-07-23 14:27:07 UTC
Evolution 2.29.3 I have exchange and IMAP account configured. I marked exchange Inbox for offline usage, synced the mails, went offline, opened 3-4 mails, later i switched from offline to online, reading mail in my IMAP account, evolution crashed in the middle. gdb traces of evolution (evolution:13151): camel-exchange-provider-CRITICAL **: is_online: assertion `ed->estore != NULL' failed (evolution:13151): camel-exchange-provider-CRITICAL **: is_online: assertion `ed->estore != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xa6cf9b90 (LWP 13767)] 0xb24da535 in camel_exchange_utils_sync_count (service=0x80a5ad8, folder_name=0xa5a5d7e8 "personal/Inbox", unread_count=0xa6cf9244, visible_count=0xa6cf9240, ex=0xa6cf9294) at camel-exchange-utils.c:2307 2307 *visible_count = mfld->messages->len; (gdb) t a a bt
+ Trace 219562
Thread 86 (Thread 0xa6cf9b90 (LWP 13767))
(gdb)
Created attachment 154035 [details] test eex patch for evolution-exchange; I saw this only once, but after that I was unable to reproduce it. Very bad. Could you try with this patch and paste the output of it here, please? Just note that for me the finalize on a Service is never called, I do not know why, it's probably kept somewhere in Evolution internal structures. Based on the results we can try to follow up on the patch to find out the core issue, in case you are able to reproduce it reliably. Thanks.
*** Bug 630966 has been marked as a duplicate of this bug. ***
*** Bug 631854 has been marked as a duplicate of this bug. ***
Downstream bug report about the same in 2.32.0: https://bugzilla.redhat.com/show_bug.cgi?id=649557
*** Bug 639944 has been marked as a duplicate of this bug. ***
*** Bug 647740 has been marked as a duplicate of this bug. ***
The "evolution-exchange" package only supports Exchange 2000 and 2003 servers. Newer versions such as Exchange 2007 and 2010 are not supported by "evolution-exchange". It is required to use the package "evolution-ews" (or to some extend "evolution-mapi") for newer version fo Exchange servers. If the problem/request described in this report still happens with a recent version of "evolution-ews" or "evolution-mapi", please add a comment to this report (and update the "product" setting accordingly if possible). There are currently no plans to continue the development of the package "evolution-exchange", so this report will soon be closed as WONTFIX. Thanks for your understanding and sorry that the reported problem was not solved in time in the package "evolution-exchange".
evolution-exchange only supports the older Microsoft Exchange server versions 2000 and 2003. The last stable release of evolution-exchange was 3.4.4 which took place a year ago. evolution-exchange is now deprecated and not under active development anymore. It is unlikely that there will be any further active development. Closing this report as WONTFIX as part of Bugzilla Housekeeping. Please feel free to reopen this bug report in the future if anyone takes the responsibility for active development again. Also feel free to reopen this ticket and change the "Product" field accordingly if the reported issue still happens with a recent version (newer than version 3.6) of one of those Exchange backends that are still supported. Please see https://help.gnome.org/users/evolution/3.8/exchange-connectors-overview.html for more information on available backends.