Comment 18 for bug 1311213

Thanks for a bug report. I agree with a blame to evolution-ews, on the first look at least. To be sure, it'll be good to see what evolution does and why it is frozen. Could you do the following, please?
a) install debuginfo packages for evolution-data-server, evolution and
   evolution-ews; make sure the package version matches version of the binary
   package (rpm -qa | grep evolution | sort)
b) reproduce the issue
c) while the evolution is frozen, invoke these two commands from a terminal:
   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>evo-bt.txt
   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution-calendar-factory` \
     &>ecf-bt.txt

d) please review the content of evo-bt.txt and ecf-bt.txt for any private
   information it can contain, like email addresses, server addresses and
   passwords (I usually search for "pass" (quotes for clarity only) at least).

Once you've the file content sanitized, upload it here, please, and I'll check where the evolution is stuck. I would guess it's waiting for a response from the evolution-calendar-factory process, which might be busy with an update of the EWS calendar.

It would be also good to restart the machine before starting this reproducer, just to make sure all updated binaries will be running as expected.