Created attachment 892761 [details]
screenshot of evolution

Thanks for a bug report. I see in the backtrace that it is related to your IMAP account. I made any fixes in it after 3.12.1 release, which will be part of 3.12.2. It'll be good to retest with it, once it'll be released and it'll enter the COPR repository. The release date of 3.12.2 is set on May 12th.

I seem to be having the same issue as this (also, issue 1016119 could be a duplicate?) where Evolution 3.12.4-1.fc20 is hanging/going into an infinite loop syncing a large amount of IMAP folders. The UI becomes unusable due (I can still select folders but nothing actually happens).

I appreciate the rhughes gnome 3.12 COPR, but there seems to be no support for selectively upgrading evolution to 3.12 while leaving the rest of the desktop at f20. So I would appreciate a backport as Evolution is basically unusable for me.
This happens usually at startup (about 75% of the time) or when waking up from sleep (about 50% of the time).

Doing "a backport of 3.12.x to Fedora 20) is not that simple, that's why the COPR repository exists, because it takes care of dependencies. There might be some reason for the folder refetch, I would guess it's due to Quick resync misbehaving [1], where usually helped to disable quick resync in account's properties, but it can be also anything else. Installing debuginfo packages for evolution-data-server and evolution, then getting backtrace of running (and busy) evolution in this state with this command:
   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
would help with identification what evolution does. Please check the bt.txt for any private information, like passwords, email address, server addresses,... I usually search for "pass" at least (quotes for clarity only).

Also grabbing the log of IMAP activity may help, this can be grabbed by:
   $ CAMEL_DEBUG=imapx:io evolution &>log.txt
but this log contains raw communication between the server and the evolution, which means even more private information than the bt.txt (as it logs the communication, it can contain every message or its headers which will be downloaded during the logging).

[1] https://bugzilla.gnome.org/show_bug.cgi?id=719328

This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.