Red Hat Bugzilla – Bug 829192
Evolution hangs after resume or after pulling the network cable
Last modified: 2012-06-08 05:17:52 EDT
Description of problem:
Evolution does not handle lost connection properly, it becomes unresponsive and can only be killed with SIGKILL. This happens after a suspend/resume, but also after pulling the network cable (and putting it back).
I use evolution with imap+ over SSL and SMTP over SSL (3 accounts).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start evolution with imap+ accounts over SSL
4. try to use evolution
Evolution hangs. It rare cases is even possible the cache ($HOME/.cache/evolution) is corrupt and this needs to be removed (rm -fr .cache/evolution) to make it operational again.
Thanks for a bug report. The network issue is already reported as . Please see it for any further updates.
The ~/.cache/evolution corruption issue, I would say it's sort of expected, when you kill the application, which can be in time when it is in the middle of writing data into the cache. Luckily the cache is only a local copy of server data, thus you are not loosing any data.
Also switching from online modus to offline makes evolution hang.
In my case, all these issues are gone when switching from IMAP+ to IMAP. So it looks like evolution does not handle limitations of the imap server in a robust way (at least when IMAP+ is used, but maybe it is not limited to that).