GNOME Bugzilla – Bug 625018
Crash in e_source_list_sync at e-source-list.c:721
Last modified: 2013-07-23 14:30:36 UTC
evolution 2.31.6 Just enabled already configured account from preferences. ** (evolution:10459): WARNING **: LDAP authentication failed (0x31 (Invalid credentials)) [New Thread 0xa9262b70 (LWP 10481)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xa9a63b70 (LWP 10478)] IA__g_type_check_instance_cast (type_instance=0x8a73de0, iface_type=135210744) at gtype.c:3970 3970 gtype.c: No such file or directory. in gtype.c (gdb) t a a bt
+ Trace 222958
Thread 18 (Thread 0xa9a63b70 (LWP 10478))
Thread 1 (Thread 0xb625f870 (LWP 10459))
(gdb)
Downstream bug report about the same from 2.32.1: https://bugzilla.redhat.com/show_bug.cgi?id=681177
Thinking of it, this, and similar, might be addressed by a fix for bug #623933
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.