Comment 14 for bug 633352

I have 2 events that I dismiss every time Thunderbird launches.

Here is the debug info for them emitted during Thunderbird startup:

[calAlarmService] considering alarm for item: Update: TIGER ONLY: SDN Post Mortem and Workout alarm time: 2010/11/15 21:15:00 UTC isDate=0 snooze time: 2010/11/15 21:15:00 UTC isDate=0
[calAlarmService] now is 2010/12/07 23:44:49 UTC isDate=0
[calAlarmService] last ack was: 2010/11/15 21:14:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

[calAlarmService] considering alarm for item: Tiger Thanksgiving alarm time: 2010/11/19 18:45:00 UTC isDate=0 snooze time: 2010/11/19 18:45:00 UTC isDate=0
[calAlarmService] now is 2010/12/07 23:44:49 UTC isDate=0
[calAlarmService] last ack was: 2010/11/19 18:44:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

It seems that the problem is that Thunderbird thinks the last acks (dismissal I presume?) were 2010/11/15 and 2010/11/19, when in fact, I actually dismiss these two events every time I start Thunderbird so the last acks for both these events should be 2010/12/07.

Now if I try to dismiss these reminders, I see:

[calAlarmService] considering alarm for item: Update: TIGER ONLY: SDN Post Mortem and Workout alarm time: 2010/11/15 21:15:00 UTC isDate=0 snooze time: null
[calAlarmService] now is 2010/12/07 23:51:55 UTC isDate=0
[calAlarmService] last ack was: 2010/12/07 23:51:55 UTC isDate=0
[calAlarmService] Update: TIGER ONLY: SDN Post Mortem and Workout - alarm previously ackd.

[calAlarmService] considering alarm for item: Tiger Thanksgiving alarm time: 2010/11/19 18:45:00 UTC isDate=0 snooze time: null
[calAlarmService] now is 2010/12/07 23:52:31 UTC isDate=0
[calAlarmService] last ack was: 2010/12/07 23:52:31 UTC isDate=0
[calAlarmService] Tiger Thanksgiving - alarm previously ackd.

So that's weird, it seems that it doesn't update the last ack because this code thinks the last ack was already updated. This would be fine if it did in fact update the ack time, but if I quit Thunderbird and launch it again, I see again:

[calAlarmService] considering alarm for item: Update: TIGER ONLY: SDN Post Mortem and Workout alarm time: 2010/11/15 21:15:00 UTC isDate=0 snooze time: 2010/11/15 21:15:00 UTC isDate=0
[calAlarmService] now is 2010/12/07 23:54:42 UTC isDate=0
[calAlarmService] last ack was: 2010/11/15 21:14:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

[calAlarmService] considering alarm for item: Tiger Thanksgiving alarm time: 2010/11/19 18:45:00 UTC isDate=0 snooze time: 2010/11/19 18:45:00 UTC isDate=0
[calAlarmService] now is 2010/12/07 23:54:42 UTC isDate=0
[calAlarmService] last ack was: 2010/11/19 18:44:59 UTC isDate=0
[calAlarmService] alarm is in the past and unack'd, firing now!

So the code that checks for alarms is still seeing the old last ack time.