GNOME Bugzilla – Bug 603132
evolution crashed : switched from offline to online
Last modified: 2013-07-23 14:31:52 UTC
Evolution 2.29.2 Clicked on icon at status bar to change state. (evolution:4753): camel-exchange-provider-WARNING **: got_folder_props: 4 [Thread 0xa2ef8b90 (LWP 8343) exited] (evolution:4753): camel-exchange-provider-CRITICAL **: get_camel_folder: assertion `mfld->ed->estore != NULL' failed [Thread 0xa52ffb90 (LWP 8341) exited] evolution-shell-Message: Online preparations complete. [New Thread 0xa52ffb90 (LWP 8344)] [New Thread 0xa2ef8b90 (LWP 8345)] [New Thread 0xa3efab90 (LWP 8346)] [New Thread 0xa26f7b90 (LWP 8347)] [Thread 0xa3efab90 (LWP 8346) exited] (evolution:4753): camel-WARNING **: Trying to check junk data is OBJECT 'CamelService' (evolution:4753): camel-CRITICAL **: camel_object_cast: assertion `check_magic(o, ctype, CAMEL_OBJECT_MAGIC)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xaa7ffb90 (LWP 8328)] 0xb7c19a1a in camel_service_get_session (service=0x0) at camel-service.c:587 587 return service->session; (gdb) t a a bt
+ Trace 219319
Thread 1 (Thread 0xb6393720 (LWP 4753))
Created attachment 154388 [details] debug eex patch for evolution-exchange; I'm not sure whether this will shed some light on the issue, but let's see. Please give it a try. There will be written on the console new messages about 'mfld' and 'ed' pointers used in particular functions. Thanks.
Damn. i cann't reproduce the crash now :-( I have tried 5-6 times but evolution didn't crash for me. I will keep patch in sources and provide more info if i get crash any time later.
bug 625570 may be a dupe
*** Bug 646668 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.