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 214001 - evolution exiting
evolution exiting
Status: RESOLVED DUPLICATE of bug 211984
Product: evolution
Classification: Applications
Component: Calendar
unspecified
Other All
: Normal normal
: ---
Assigned To: Federico Mena Quintero
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2001-10-30 09:11 UTC by Jake West
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jake West 2001-10-30 09:04:37 UTC 
Package: Evolution
Priority: Normal
Version: 0.16.99
Synopsis: evolution exiting
Bugzilla-Product: Evolution
Bugzilla-Component: Miscellaneous

Description:
When evolution exits, it always fails to kill the following process:  
evolution-alarm-notify --oaf-act
I believe this has led to problems before (after restarting a new
evolution), which is why I always manually kill it, but that seems like
a problem that could be easily fixed.
Comment 1 Luis Villa 2001-10-30 14:56:22 UTC 
I'm fairly certain that this is the alarm daemon and is not intended
to die except in case of upgrade/restart. care to comment, federico?
Comment 2 Federico Mena Quintero 2001-10-30 18:50:54 UTC 
It is not intended to exit because you may have alarms in the future
and the alarm daemon cannot know for how long you will be running your
session.

I am going to modify the alarm daemon to exit if there are no future
alarms at all, and to have the Wombat re-start it if someone adds an
appointment with an alarm in the future.
Comment 3 Federico Mena Quintero 2001-11-01 19:09:16 UTC 

*** This bug has been marked as a duplicate of 211984 ***
Comment 4 Luis Villa 2001-11-26 17:04:29 UTC 
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be
moving a large number of bugs around in the bugzilla. You can just
search on 'body contains' 'Because of the decision to remap' and mark
all as read. Please direct all questions about this change to
evolution@ximian.com, not the bug.
Luis