262332 - Task alarms set for due date fire late (if at all)

Status: VERIFIED WORKSFORME

(Calendar :: General, defect)

Description

[Jeff Beal]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10

Over the course of the last two days, I have created five tasks with alarms. 
For four of these, I set the alarm for a few minutes prior to the task due date.
 None of those alarms fired at the given time.  For the fifth task, I set a
start time and set the alarm for 1 minute prior to the start time; the alarm
fired as expected.

For the first of those tasks for which I set an alarm, I received an alarm
approximately 26 hours after the due date.  I have not yet reached 26 hours past
the other alarms, but will not mark them complete, just to see what happens.

I am running the latest release of Mozilla Calendar Extension for Thunderbird 0.8

Reproducible: Always
Steps to Reproduce:
1.Create a new task
2.Specify a due date
3.Set an alarm for a few minutes prior to the due date (I have used 1 and 5)

Actual Results:  
No alarm at the specified time; in one case, the alarm fired 26 hours after the
due date.

Expected Results:  
Fired an alarm at the specified time

Comment 1

[Joey Minta]

Reporter:
    New builds of calendar have been released since you filed this bug.  In
order to keep things current, can you please say whether or not you are still
experiencing this bug with the latest builds?

Comment 2

[Jeff Beal]

(In reply to comment #1)
> Reporter:
>     New builds of calendar have been released since you filed this bug.  In
> order to keep things current, can you please say whether or not you are still
> experiencing this bug with the latest builds?

Verified last week with Release 0.2.  Downloaded latest nightly (which appears
to be older than Release 0.2) and confirmed there, as well.  I experimented
further, and found that the alarm goes off correctly if I specify a start time
for the task (even if the alarm type is "before task is due")

Steps to reproduce:
1) Create a new task; leave start date/time blank and specify a due date fifteen
minutes in future.
2) Set an alarm to fire ten minutes before task is due (the default when no
start date is specified)
3) Allow five minutes to pass; alarm will not fire
4) Edit the task and specify a start time (any start time).  Alarm will fire
when you save the task.

Comment 3

[Joey Minta]

Confirmed in 2005011112-cal for FF/Linux, using steps outlined in comment #2 to
reproduce.

Status: NEW
Hardware: All
OS: All

Comment 4

[Jeff Beal]

Just checked this on Sunbird nightly build on Windows platform.  (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20051220 Mozilla Sunbird/0.3a1+)  Everything looks good with this issue.

Comment 5

[Jeff Beal]

Would you mind justifying your WORKSFORME fix?  Joey confirmed that this was an actual bug.  I am confirming that it is now fixed.  I thought WORKSFORME was a flag to indicate that something wasn't a repeatable bug, and this most certainly was.

Comment 6

[Robin Edrenius]

(In reply to comment #5)
> Would you mind justifying your WORKSFORME fix?  Joey confirmed that this was an
> actual bug.  I am confirming that it is now fixed.  I thought WORKSFORME was a
> flag to indicate that something wasn't a repeatable bug, and this most
> certainly was.
> 

I think that when a fix can't be directly associated to a specific checkin, it's supposed to be marked worskforme instead of fixed. Someone please correct me if I'm wrong though.

Comment 7

[Joey Minta]

VERIFIED.  We only do FIXED if there's a specific checkin or bug we can point to.

Comment 8

[Jeff Beal]

Thanks for the clarification.