GNOME Bugzilla – Bug 323115
--force-shutdown does not shutdown e-d-s
Last modified: 2013-09-10 14:04:04 UTC
The --force-shutdown option does not shutdown e-d-s since 2.4, like it used to. This is a bad thing. Please add this feature back in, as described in the help: $ evolution-2.4 --help | grep -A 1 force-shutdown --force-shutdown Forcibly shut down all Evolution components This is a regression.
...or the parameter explanation should be changed - i know that there are applications that require e-d-s to keep running (e.g. gnome clock applet) anyway, confirming.
Evo, clock-applet, contact-lookup-applet, gaim, gnomemeeting, ... They all use (or at least can use) e-d-s. If e-d-s is not running, those apps just have to restart it. This is no big deal and is the way to go. This very same approach worked perfectly in GNOME 2.10. There is no reason for this and forcing the user to *kill* e-d-s if need be. For example, there is no way to move entire accounts without this. And killing e-d-s might lose data. That#s what a graceful shutdown is for. Regression.
I would like to be able to restart e-d-s without killing it myself, please fix me! Well the bug, not me, but you know what I mean.
also see bug 253484 and bug 253904
Please, oh please -- do NOT make me go through the hell of using 'kill' when talking clueless users through the steps to recreate their important data. 'evolution --force-shutdown' *really* has to stop e-d-s. Respawning is fine. I don't care. But it must be shut down gracefully. I am serious. Get this in ASAP. Whoever wants to argue about this should read the IRC logs *first*.
Do not make me go though this... "yet another 6 months and yet another major Evo version" I mean. The need to use this *ugly* hack to recreate BerkeleyDB files in 2.4 is more than enough. Considering tonight, it is more than I can take already.
booooy, just wrote the same mail, explaining "ps ax|grep" and kill. this really sucks.
Yes right. evolution/tools/killev.c (main) add_matching_repo_id ("IDL:GNOME/Evolution/Component:" BASE_VERSION); add_matching_repo_id ("IDL:GNOME/Evolution/DataServer/CalFactory:" DATASERVER_API_VERSION); add_matching_repo_id ("IDL:GNOME/Evolution/DataServer/BookFactory:" DATASERVER_API_VERSION); add_matching_repo_id ("IDL:GNOME/Evolution/Importer:" BASE_VERSION); add_matching_repo_id ("IDL:GNOME/Evolution/IntelligentImporter:" BASE_VERSION); add_matching_repo_id ("IDL:GNOME/Spell/Dictionary:0.3"); It uses BASE_VERSION which is 1.6 (now), but the IDL File uses IDL:GNOME/Evolution/Importer:API_VERSION (1.2) in eds. Harish is looking into the issue.
Created attachment 57170 [details] [review] Fix that sets the oafids to the api version rather than the base version No..the above code in Evolution is just fine. It is the oafids in EDS that need to be corrected. Posted a patch for review. 2.4 requires a different patch with the same logic. shall post it tomorrow.
A very similar patch wouldn't happen to fix bug 323115 too, would it?
Doh! I mean bug 323116.
Right. I will add the change along with the fix for the gnome-2-12 branch.
Harish, Looks fine. Tried and it worked too ;-)
Created attachment 57330 [details] [review] Exchange connector part of it.. With the above patch, exchange address books and calendars are not getting loaded. Attached the fix for the same.
OK, if I understand the recent comments correctly, this is going to fix this issue for e-d-s and exchange-storage in one fell swoop. Going to mark bug 323116 a duplicate of this then and adjust the summary. Please re-open bug 323116 if these fixes are *not* going to address the exchange-storage issue for HEAD and gnome-2-12 branch as well. And please confirm both issues are going to be fixed in both branches. TIA.
*** Bug 323116 has been marked as a duplicate of this bug. ***
Summary adjusted. Thanks for trying to keep me sane. :)
No - 323116 is not a dupe of this bug. restoring the summary back.
Created attachment 57580 [details] [review] Another patch for exchange connector. Corrected the DataServer BookFactory and CalFactory versions also.
Committed exchange connector fixes to gnome-2-12 branch,
Now I'm confused. This bug already was CLOSED FIXED, and after that a patch is being committed to gnome-2-12. What's the exact status of this bug? Are *all* relevant bits committed to HEAD and the stable gnome-2-12 branch?
*poke* Does anyone care to explain comment 21? Adding Sushma to the Cc list.
Patches are committed to both stable gnome-2-12 branch and cvs head.