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 732873 - You must be working online to complete this operation.
You must be working online to complete this operation.
Status: RESOLVED DUPLICATE of bug 731585
Product: evolution-ews
Classification: Other
Component: Mail
3.12.x
Other Linux
: Normal major
: ---
Assigned To: Evolution EWS maintainer(s)
Evolution EWS maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-07-07 23:47 UTC by Markus Dorfer
Modified: 2014-07-08 16:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Markus Dorfer 2014-07-07 23:47:55 UTC 
Hi,

Sorry to use the same title but it is not like the error mentioned in 708175.

Since the release 3.12.3 exchange access is not working for me anymore. 

the bug is also already here: https://bugs.archlinux.org/task/41007?project=1&cat%5B0%5D=2&string=evolution-ews

It is working with older releases like 3.10 and also like in the bug reported said in 3.13. I tried it with Arch and Fedora. 

on arch it worked with a downgrade to 3.10 and also with the upgrade to 3.13.

on fedora I upgraded with the external repositories of rhughes to gnome 3.12 and got the same behaviour with 3.10.4 on fedora i have no problems.

in the arch bug they mention the following commit maybe it has something todo with it. 

https://git.gnome.org/browse/evolution-ews/commit/?h=evolution-ews-3-12

thx

markus
Comment 1 Markus Dorfer 2014-07-08 15:10:38 UTC 
found out which version is working and which not in fedora

evolution-ews-3.12.1 is working.
evolution-ews 3.12.2 and up is not working anymore.

recompiled the fedora 21 packages to test that out from the koki build system.
Comment 2 Milan Crha 2014-07-08 16:29:44 UTC 
Thanks for a bug report. I believe you face bug #731585, thus I mark this as a duplicate of it.

*** This bug has been marked as a duplicate of bug 731585 ***