GNOME Bugzilla – Bug 226100
When exiting Evolution, the process evolution-alarm-notify does not die.
Last modified: 2005-11-03 06:43:28 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: When exiting Evolution the evolution-alarm-notify process does not die. It can be killed by hand fine. Steps to reproduce the problem: 1. Start Evolution 2. Syn or read mail, or do something. 3. exit Evolution 4. run 'ps -ef | grep evolution' Actual Results: Process "evolution-alarm-notify" is still in the process list. Expected Results: All evolution processes should go away. How often does this happen? Every time Additional Information: I am getting some timeouts with my exchange server when sending messages and when getting calander information but I think that may be a different issue (I hope). Running Connector to an Exchange server. RedHat is fully patched using Ximian Red Carpet.
The alarm daemon must keep running, to inform the user about the alarms. If we kill it, alarms won't work until you restart evolution.
Why must the alarm daemon keep running for Evolution when Evolution has been stopped? When you exit a program all the pieces should go away. If the alarm daemon is for Evolution, what alarms should it notify the user about when Evolution is no longer running? It isn't running when until I start Evolution so why must it run after Evolution has exited?
If you set up an alarm to go to the dentist, for instance, and have quitted evolution, the user would expect to be notified of the event (if he's set up an alarm for it) even if evolution (the shell) is not running. And yes, it is running when you log in, since it is kept running, and the gnome session restarts it when you log in to GNOME, even if evoilution is not started. Of course, this only happens if it was running when you closed your GNOME session.
Pardon my ignorance. I momentarily went into MS Lemming mode and expected this to operate like an MS program and not like I would expect a true alarm to operate. Keep up the good work.
I reopen this bug after long discussions on the IRC. The rest is up to Ximian people. :)
This is more than a "wishlist" bug. In multiuser environments it is extremely annoying that all the users who have used Evolution will have their gconfd-2 processes running in the background even after they have logged out, reserving considerable amounts of memory. It's even worse that this bug also makes it impossible for a user to log out and log in again without manually killing the evolution-wombat and evolution-alarm-notify processes before logging back in. Otherwise the configuration daemon will not be started correctly (because it's already running), which causes the settings to be set back to the defaults and panel applets to not start at all. Could it be possible to redesign alarm-notify so that it would be running in the system tray, for example, rather than as an invisible background process?
*** bug 249352 has been marked as a duplicate of this bug. ***
Marking this as duplicate of 225828 as the decision/patch for that bug applies to this bug as well. *** This bug has been marked as a duplicate of 225828 ***
Also please look at this http://mail.gnome.org/archives/evolution-patches/2005-November/msg00001.html to get patch that adds e-a-n to system tray.