After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 741914 - Evolution should have a kill watchdog triggered on exit to prevent stuck mail operations from preventing quitting the application
Evolution should have a kill watchdog triggered on exit to prevent stuck mail...
Status: RESOLVED DUPLICATE of bug 545153
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal enhancement
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-12-23 15:39 UTC by Jean-François Fortin Tam
Modified: 2015-01-07 15:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2014-12-23 15:39:32 UTC
I don't particularly love recommending a "solution" like this, but I'm thinking of non tech-savy users who can't be expected to kill processes or run "evolution --force-shutdown" all the time.

When I ask to quit an app, I expect it to quit, whatever happens, within 15 seconds maximum.

Currently, and for the past few releases (3.12 going all the way back to 3.6 and such), about half of the time where I want to quit it there's always "something" hanging up Evolution, be it a permanently stuck "refreshing folders for $account", "reconnecting to server for $account", "checking folder INBOX" or something like that. Evolution has this tendency to hang a lot in its IMAP operations. When it does, I naïvely click the Close button in the hope that it stops whatever it's trying to do, shuts down and restarts from a clean state.

And most of the time when I do that (everytime?) I end up needing to alt+F2 and run "evolution --force-shutdown" and wait 10-20 more seconds. Then this brings the question: why not do that for me in the first place?
Comment 1 Milan Crha 2015-01-07 15:15:36 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 545153 ***