After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 451678 - Connector freezes if OWA server unreachable, can't be started in offline mode.
Connector freezes if OWA server unreachable, can't be started in offline mode.
Status: RESOLVED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.10.x
Other All
: High critical
: ---
Assigned To: Connector Maintainer
Ximian Connector QA
Depends on:
Blocks:
 
 
Reported: 2007-06-27 17:56 UTC by mjs
Modified: 2009-06-23 07:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18

Attachments
Stack trace from hung Evo process. (8.86 KB, text/plain)
2007-09-30 23:49 UTC, mjs 		Details

Description mjs 2007-06-27 17:56:14 UTC 
Steps to reproduce:
1. Set up an exchange account.
2. Start Evo when OWA server is unavailable.
3. Enter password when prompted.


Stack trace:
No stack trace available.  Evo simply becomes totally unresponsive and must be killed manually.

Other information:
Even if started from the command line with --offline option, connector still prompts for OWA password and freezes if it can't connect.

I'm trying to find out the exact nature of the OWA server failure--will report it here when I do.  But the --offline option to Evo should prevent any attempt to contact the server.  That way, one could at least disable the Exchange accounts and continue to work with other accounts.
Comment 1 mjs 2007-06-29 23:52:06 UTC 
OK The freeze actually happens when the mail notification applet is set to use Evolution to monitor an Exchange mailbox.  I'll file a separate bug for that (I'll start against mail-notification-evolution-plugin, but I suppose the issue could be here as well).  But the problem with the connector not starting offline is still an issue.
Comment 2 Tobias Mueller 2007-09-21 21:18:56 UTC 
Could you attach a gdb when evo is unresponsive? If so, you could get a stacktrace :)

Please see http://live.gnome.org/GettingTraces/Details for more information on how to do so. Thanks in advance!
Comment 3 mjs 2007-09-30 23:43:53 UTC 
Sorry to take so long.  I am attaching a stack trace from the hung process.

Since the original filing, my server admin has made the OWA connector accessible outside the firewall.  But the global contact connector is not available outside the firewall.  But the behavior is the same: without VPN, Evo hangs on connection.  With VPN, it works OK.
Comment 4 mjs 2007-09-30 23:49:42 UTC 
Created attachment 96439 [details]
Stack trace from hung Evo process.
Comment 5 Bharath Acharya 2009-06-23 06:59:29 UTC 
If password authentication keeps failing, we now disable the prompts and hence you'll be able to continue using and playing with the other accounts configured. So the fix for bug #307410 should fix the issues that you mentioned in here. Give it a try and reopen the bug if it still fails.
Comment 6 Bharath Acharya 2009-06-23 07:00:51 UTC 
BTW it is part of 2.12 release