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 225828 - shutdown evolution-alarm-notify after Evo is closed
shutdown evolution-alarm-notify after Evo is closed
Status: RESOLVED WONTFIX
Product: evolution
Classification: Applications
Component: Calendar
2.4.x (obsolete)
Other All
: Normal enhancement
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
: 211984 226100 249448 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-05 15:19 UTC by Toni Willberg
Modified: 2012-02-25 05:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Toni Willberg 2002-06-05 15:19:31 UTC 
Hi.

When Evolution is closed the evolution-alarm-notify (and perhaps some other
components) still running. I thought that this was a bug, but was told it's
a feature. :)

It would be nice if Evolution would use a dialog to ask user if he wants to
leave those components running after closing Evolution. 

There has to be also "[X] Don't ask me again." so it would not annoy user
if he does not want to see the dialog. It should be also configurable in
preferences if that dialog is shown or not.

- Toni "Tonyx" Willberg
Comment 1 Calum Benson 2005-07-28 10:36:22 UTC 
Apologies for any spam... cc'ing usability-maint on all Evolution usability
bugs. Filter on EVO-USABILITY-SPAM to ignore.
Comment 2 Chakravarthi 2005-09-26 05:30:30 UTC 
point well taken ..
The reporter is referred to 
http://go-evolution.org/Evo-Alarm-2.6 to add his/her comments
Comment 3 Toni Willberg 2005-09-26 08:22:11 UTC 
I suggest the Evolution team transfers the RFE's from Bugzilla to the wiki
instead. The reporters don't necessarily have an account on go-evolution.org.

Having multiple places to maintain is too much for regular end-user complaining
about features. ;)
Comment 4 Harish Krishnaswamy 2005-09-27 04:07:47 UTC 
The wiki is more fluid and discussion on new stuff fluctuates depending on the
stage of development in a release cycle. The Bugzilla has been and is the
preferred place for reporting/tracking RFEs in the long term. If the reporters
are used to it, there is no point in asking them to change. Besides, the wiki
would not remain much useful if it is deluged with all the RFEs in Bugzilla and
fresh reports. I feel it is perhaps more easier for the team to post
RFEs-I-think-should-be-discussed-now onto the wiki.
Comment 5 Chakravarthi 2005-11-03 06:42:00 UTC 
*** Bug 226100 has been marked as a duplicate of this bug. ***
Comment 6 Chakravarthi 2005-11-07 06:32:40 UTC 
Call your attention to a patch located at 
http://mail.gnome.org/archives/evolution-patches/2005-November/msg00001.html
which adds an UI to alarm-notification-process
Gives a solution to this problem as - 
user can explicitly diable alarms or exit e-a-n independently of evolution.
This solution is half-way between solution requested here and the request 
that e-a-n must exit when there are no future alarms... as in 211984
Comment 7 Chakravarthi 2005-11-07 06:33:12 UTC 
*** Bug 211984 has been marked as a duplicate of this bug. ***
Comment 8 André Klapper 2005-12-26 13:05:58 UTC 
still valid in 2.4, targetting this to force a decision.
as already written, a patch is available.
Comment 9 Luis Villa 2006-02-06 16:49:03 UTC 
*** Bug 249448 has been marked as a duplicate of this bug. ***
Comment 10 Matthew Barnes 2008-03-11 00:25:43 UTC 
Bumping version to a stable release.
Comment 11 Matthew Barnes 2012-02-25 05:09:26 UTC 
Closing as WONTFIX since alarm-notify should stay running at all times.