Bug 1402607

Thanks for a bug report. You can run evolution from a terminal as:

   $ EWS_DEBUG=2 evolution

to see what the evolution-ews does, as with that command you'll see a raw communication between the server and the client. To see where exactly the evolution is stuck you can get a bactrace of the evolution process when it's in that state. To have a useful backtrace, please install debuginfo packages for the evolution-data-server, evolution and evolution-ews. One way to install those packages is to use dnf as root:

   $ dnf install evolution-data-server-debuginfo evolution-debuginfo \
       evolution-ews-debuginfo \
       --enablerepo=fedora-debuginfo \
       --enablerepo=updates-debuginfo

Make sure that the package version of the debuginfo matches the binary package version.

You can get the backtrace with command like this:
   $ gdb --batch --ex "t a a bt" -pid=`pidof evolution` &>bt.txt
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).

I was away for a day.  I just restarted Evolution and what I see now is a bit different.

The window is no longer unresponsive.   I can click on messages and they appear in the right pane.  I can also switch to the Calendar and interaction with that seems to be normal.

When viewing Mail, there are still two tasks at the bottom on the screen.  The first task is labeled "Retrieving message 'X' in Inbox" where X is a very long alphanumeric string that appears to be a message ID.  The message ID seems to be updated about once per second.

After a while (I'm not sure how long, I was gone), the tasks cleared up and Evolution was working normally again.

I briefly tried to recreate the state from Wednesday by starting and stopping a VPN.  However, I was unable to recreate the problem.

Thanks for the update. Either a Junk filtering or simply a download for an offline usage can cause a full message download. Hard to tell which of the two are related here, if any. It can be that the offline download finished eventually, after a long time, then the next time it tried it figured that all messages are downloaded, thus didn't redo it.

If this is related to the download for offline usage, then I'd suggest to close this in favour of an upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=773419

Created attachment 1234472 [details]
Evolution debug log while stuck

When I came to work today, Evolution was getting stuck trying to retrieve the contents of a message.  So, I forced it to exit.  I then restarted it with EWS_DEBUG=2.  The attached file is the output while Evolution was stuck.

I wasn't able to get a backtrace this time.  Hopefully, the next time this happens, I'll have more time for that.

I just noticed that my computer had run out of physical memory and was using the swap partition.  After I closed an Epiphany window, a lot of memory seemed to be freed up.  This seems to have helped with the responsiveness of Evolution.

Thanks for the update. The log shows a usual start of tan EWS account, it checked for the changes and then started listening for the server changes.

If you've got out of the physical memory then it can be just it. The evolution is slowed down due to the swapping. There is not much to do from the evolution side, unless it's being evolution itself using so much memory (where you indicated it's related to Epiphany instead; it would worth a bug report there for sure).

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.