[Bug 1311213] [NEW] Evolution 3.10.4 with EWS plugin: Calendar locks up application

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Sebastien Bacher (seb128):

I ran into what appears to be a nasty bug with running the Evolution
email client 3.10.4 downloaded from the Ubuntu 14.04 Software Center
with the Exchange Web Services (EWS) plugin.

After configuring my work Exchange account using EWS, email, contacts,
and calendar reminders appear to be working with no problems. Yet, when
I click on the Calendar button to view my calendar and change to Month
view, Evolution completely locks up. I manually killed all Evolution-
related processes using the system monitor, but re-launching Evolution
takes me back directly to the Calendar, freezing the email client once
again. If I wait long enough (about 15 - 20min) the email client seems
to return back to normal, but will freeze again if I click Calendar once
more. I was able to recreate the issue on a VM as well. I also verified
the issue exists with vanilla Ubuntu Desktop 14.04 and Ubuntu GNOME
14.04. All tests were run and confirmed on 64-bit releases.

I did a little research before posting and found someone had the exact
same problem with Evolution running on Fedora. The original link can be
found here:

https://bugzilla.redhat.com/show_bug.cgi?id=1075461

The issue appears to be with the evolution-data-server component, and a
patched version of the component evolution-data-server-3.10.4-3 was
released to resolve the issue. I tried looking online for an Ubuntu
compatible version of the patch but have fallen short.

** Affects: evolution-data-server (Ubuntu)
     Importance: High
         Status: Triaged

** Affects: evolution-ews (Ubuntu)
     Importance: High
         Status: Invalid

** Affects: evolution-data-server (Fedora)
     Importance: Unknown
         Status: Unknown


** Tags: evolution evolution-calendar evolution-ews patch
-- 
Evolution 3.10.4 with EWS plugin: Calendar locks up application
https://bugs.launchpad.net/bugs/1311213
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.