GNOME Bugzilla – Bug 569716
evolution hangs during startup when global catalog server is not reachable
Last modified: 2013-07-23 14:34:36 UTC
Please describe the problem: When the global catalog is not reachable at all, evolution hangs Steps to reproduce: 1. fill in a not existing global catalog server ip address 2. restart evolution 3. Actual results: during startup it will hang Expected results: it will give a message that global catalog server is not reachable and continued Does this happen every time? yes. It also happens in earlier versions of evolution and i am always feeling bad about the stability of evolution-exchange Other information:
also try a not existing global catalog server and write a new mail. Evolution will try to resolve email addresses, and it will hang for some seconds before continueing.
I can confirm this bug with 2.28. It happens for me if I am in my home office. A workaround is to add the name of the global catalog server to /etc/hosts with 127.0.0.1 as IP address. This redirects the failing accesses to your own machine so that it gets an immediate reject and therefore does not hang. A proper fix would be to make Evolution multi-threaded, which would also fix the hangs while retrieving mail.
Note that the package "evolution-exchange" is deprecated nowadays. Similar functionality is now provided by "evolution-mapi" and "evolution-ews" packages. This bug was reported against a version that is now not supported anymore. Could you please check if the problem that you reported here still happens with a recent version of Evolution (like 3.2 or 3.0) by reporting back and providing both your version and the package that you use? Thanks in advance!
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.