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 269689 - Moving a snoozed alarm can create a second alarm event
Moving a snoozed alarm can create a second alarm event
Status: RESOLVED OBSOLETE
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2004-11-19 00:24 UTC by Luke Hutchison
Modified: 2009-07-22 16:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luke Hutchison 2004-11-19 00:24:19 UTC 
After hitting Snooze on an alarm, if you move the alarm to a point in the
future where it will go off again soon, you can end up with two alarm
events for the same calendar item, i.e. the alarm will go off when the
first snooze completes, and also when the alarm was supposed to go off for
the new time of the calendar item.  If you keep hitting Snooze, you now
need to snooze both alarm events.  I don't know that this is 100%
reproducible, but I've seen it a lot.
Comment 1 Luke Hutchison 2004-12-17 06:43:31 UTC 
Probably caused by the session management issue I reported in bug 270627.
Comment 2 Chakravarthi 2005-09-21 09:08:41 UTC 
There is a some cases of malfunction of e-a-n after snooze.
I do not see this on 2.4 though (tried snoozing 7 times)
Can the reporter please see if this happens for 2.4 and get back.
Comment 3 Luke Hutchison 2005-09-21 15:14:19 UTC 
I haven't seen this on 2.4, but I hardly ever use snooze these days.  It wasn't
always reproducible anyway, so I don't know what a good set of test cases might
be.  Feel free to close this if you think it's fixed.  I agree though that this
is probably related to bug 269685, as you pointed out in that bug.
Comment 4 Luke Hutchison 2006-05-10 03:50:07 UTC 
This bug is actually still present in:

# rpm -q evolution evolution-data-server
evolution-2.6.1-1.fc5.2
evolution-data-server-1.6.1-1.fc5.2

Reopening.
Comment 5 Luke Hutchison 2006-05-10 03:51:25 UTC 
See also bug 269685.
Comment 6 André Klapper 2006-05-27 21:41:52 UTC 
in evolution 2.7 (unstable), evolution-alarm-notify has been rewritten by srini so this could perhaps be fixed in the next stable version 2.8.

anyway, removing ancient target milestone.
Comment 7 Milan Crha 2009-07-22 16:00:39 UTC 
I'm closing this, as a very old thing.