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 270627 - gnome-session-properties -> save session causes two evolution-alarm-notify instances to start up
gnome-session-properties -> save session causes two evolution-alarm-notify in...
Status: RESOLVED DUPLICATE of bug 271480
Product: evolution
Classification: Applications
Component: Calendar
2.0.x (obsolete)
Other All
: Normal normal
: Future
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on: 219197
Blocks:
 
 
Reported: 2004-12-17 06:42 UTC by Luke Hutchison
Modified: 2006-08-29 11:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luke Hutchison 2004-12-17 06:42:42 UTC 
If saving the current session in gnome-session-properties while evolution
is running, an entry is created for evolution-2.0 and for
evolution-alarm-notify.  When you log out and log back in, two instances of
e-a-n are started up, meaning you get notified of alarms twice (this may
only happen if you hit snooze).  Often the second instance of the alarm is
out of sync with the first by a few minutes, but by a shorter period than
the alarm was snoozed for.

See also bug 219197.  Probably also related to bug 269689.
Comment 1 JP Rosevear 2005-01-13 21:28:55 UTC 
The alarm daemon is actually session managed.  I wonder if it is both
being saved in the session and also reloading it self through its
session code.
Comment 2 André Klapper 2005-06-14 12:06:35 UTC 
adding dependency as discussed with nags on irc.
Comment 3 André Klapper 2006-06-14 14:18:00 UTC 
luke, can you still reproduce this with a current gnome and evolution version, like gnome 2.14 and evo 2.6?
Comment 4 Luke Hutchison 2006-06-14 14:35:33 UTC 
I have definitely seen alarm come up twice in FC5, but was notified on other related bugs that I filed that the alarm code has recently been rewritten, so this should have gone away.  I didn't look to see whether there were two instances running.  I don't use "save session" anymore because of problems like this, so I don't really know the answer.

Given that GNOME 2.14 now has that location for .desktop files to allow automatic startup of services on GNOME start, is it possible that e-a-n doesn't need to save itself anymore?
Comment 5 André Klapper 2006-06-17 16:52:46 UTC 
removing old target milestone, needs to be tested in 2.7.x which includes srini's EThread rewrite of the alarm code.
Comment 6 Chenthill P 2006-08-29 11:06:20 UTC 

*** This bug has been marked as a duplicate of 271480 ***