GNOME Bugzilla – Bug 314591
Typed IP address not in local network - Evolution hang
Last modified: 2013-07-23 14:34:46 UTC
Distribution/Version: SuSE 10 1. Tried creating Exchange account 2. In OWA url typed https://164.9.168.136 3. Clicked Authenticate button and poped up for password 4. Entered password and clicked 'Ok' button Actual result: Evolution hang till network timeout period. User has to wait for a long time. How often: Always Additional info: Valid IP address is 164.99.168.136, but I missed one digit and typed wrongly as 164.9.168.136.
+ Trace 62637
Thread 1 (Thread 1099326016 (LWP 20360))
In a normal user scenario, I assume that user maynot be using IP address. So targeting this to 2.5.
Oops, sorry for the spam. I haven't confirmed the bug.
Changed target milestone as 'Surf' has told developers will set the target milestone after analyzing the bug.
A patch has been made by Fejj for fixing this. Not sure, if went in. Assigning to myself to remind me to check and close.
Cheking the Changelog would have helped ;) well, the patch has gone in for both 2-14 and head. please test and close this if it is working.
This is a libsoup timeout issue.
The patch for the hang has gone in. The other problem, the libsoup issue, which also looks like a hang, is manageable and not a bug. You can set the timeout for that using SOUP_SESSSION_TIMEOUT variable.
No patches have gone AFAIK. Please close the bug if the patch has already committed, with the details which version would have the fix and also, how to/where to set SOUP_SESSSION_TIMEOUT and also it's values.
Another similar bug http://bugzilla.gnome.org/show_bug.cgi?id=345639
Bumping version to a stable release.
*** Bug 345639 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.