236504 - Already acknowledged alarm is raised

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[Vincent Lefevre]

User-Agent:       Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7a) Gecko/20040202
Build Identifier: Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.7a) Gecko/20040202

I have the following alarm (I've just changed the summary and description):

BEGIN:VCALENDAR
VERSION
 :2.0
PRODID
 :-//Mozilla.org/NONSGML Mozilla Calendar V1.0//EN
BEGIN:VTODO
UID
 :cb26ee1e-1dd1-11b2-83c4-ce688c63f2dd
SUMMARY
 :Summary
DESCRIPTION
 :Description
CATEGORIES
 :Perso
PRIORITY
 :1
STATUS
 :COMPLETED
CLASS
 :PRIVATE
X-MOZILLA-ALARM-DEFAULT-UNITS
 :days
X-MOZILLA-ALARM-DEFAULT-LENGTH
 :25
X
 ;MEMBER=AlarmEmailAddress
 :[e-mail]
X-MOZILLA-LASTALARMACK
 :20031216T134609
DTSTART
 :20031001T000000
DUE
 :20040113T000000
DTSTAMP
 :20030930T213923Z
PERCENT-COMPLETE
 :100
COMPLETED
 :20040113T000000
BEGIN:VALARM
TRIGGER
 ;VALUE=DURATION
 ;RELATED=END
 :-P25D
END:VALARM
END:VTODO
END:VCALENDAR

This alarm was raised today! I quit Mozilla without acknowledging this alarm
again, and it was raised again just after restarting Mozilla.

Reproducible: Always
Steps to Reproduce:
1. Create the above alarm (manually?).
2. Start Mozilla (with Calendar).
Actual Results:  
The alarm is raised.

Expected Results:  
The alarm was acknowledged in the past, so nothing special should occur.

This is a bit strange. This alarm was raised while I was browsing a site related
to this alarm. But I don't see how Mozilla could know that. Or perhaps it is a
coincidence.

Comment 1

[Mostafa Hosseini]

The event reads: Alarm should go off 25 days before due date ( 20040113). That
would be 20031219. The alarm was once acknowledged on 20031216 which is before
that date. Therefore the alarm is considered as a missed alarm and goes off.
Isn't that the right behaviour?

Comment 2

[Vincent Lefevre]

Perhaps this is the right behaviour, but then the alarm should have been raised
much earlier! Why only on Fri, 05 Mar 2004 01:00:01 +0100 (date given by the
e-mail message).

The problem seems to be quite critical: this means that alarms may be raised
much later than expected.

Comment 3

[Joey Minta]

Vincent,
   Here's another old report that it would be nice if you could test again.

Comment 4

[Vincent Lefevre]

The problem was probably due to the fact that Mozilla didn't raise the alarm on
20031219, but such problems were not always reproducible. They don't seem to
occur any longer, so I'm closing the bug.

Comment 5

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!