GNOME Bugzilla – Bug 253484
EDS Should Have a --force-shutdown
Last modified: 2013-09-10 13:41:38 UTC
Description of Problem: Ive had several instances where evo dies and refuses to re-start. In each case, running --force-shutdown doesn't help - and the culprit turns out to be a still-running evolution-data-server. --force-shutdown should clean up this process as well.
Since evolution-data-server is nominally totally separate from Evolution itself, having Evolution kill it when there is something wrong with Evolution, is silly, since other apps may need the server. However, having evolution-data-server have a --force-shutdown option so that it may dispose of itself, and any backends, would probably be a good thing. Then, one could just run /usr/libexec/evolution-data-server-1.0 --force-shutdown to kill the server and any out-of-process backends.
Evolution does kill this now, further enhancements can happen post 2.0
retargetting from 1.3 to 1.5 to get rid of that busted milestones (as discussed with harish on irc). reassigning to harish.
also see bug 323115 and bug 253904
one can nowadays shutdown evolution-data-server by running "evolution --force-shutdown", see bug 323115, so i'm closing this as obsolete.