GNOME Bugzilla – Bug 671105
[regression] (re)make evolution suspend-friendly
Last modified: 2012-05-18 15:02:39 UTC
Hey, I wanted to report this a long time ago but didn't really had the time. It started in 3.2 (afaicr), not sure about the state in 3.4. Evolution is now really suspend/hibernate unfriendly. When resuming, it tries to resume the previous connections which are completely dead since a long time, and it sits there for a long time before finally stopping that. Sometimes it seems that it'll even never end. Switching to offline mode or quitting doesn't always work, because it sometime tries to close the connections before (and will never receive a FIN). Note that this is with IMAP+ accounts and *no* network-manager. Didn't find a filed bug already, hope this is not a dupe.
Basically, Evolution is not aware of suspends. The only signal we get that we're about to suspend (and the only signal available, as far as I know) is a network disconnect signal from NetworkManager.
Maybe, but before 3.2 suspend was handled just fine (I mean, at resume evolution wasn't trying to use dead connections)
And note that those connection seem to really never die, even closing evolution doesn't make them go away, the only way seems to be kill -9.
I confirm the problem, and it is driving me mad :/ For the suspend, shouldn't you get this signal : http://upower.freedesktop.org/docs/UPower.html#UPower::Sleeping ?
*** This bug has been marked as a duplicate of bug 551788 ***