324970 - missed alarms don't fire

Status: VERIFIED FIXED

(Calendar :: Internal Components, defect)

Description

[Dan Mosedale (:dmosedale, :dmose)]

Breaking this out into a separate bug so that we can fix it for Lightning 0.1 without depending on the bigger alarm cleanup.

Comment 1

[Joey Minta]

-> me

Comment 2

[Joey Minta]

Pretty much done with this, but I need to do a significant number of addDuration calls, which requires the fixes on bug 325459.

Comment 3

[Joey Minta]

*** Bug 327916 has been marked as a duplicate of this bug. ***

Comment 4

[Joey Minta]

The checkin on Bug 315051 ought to have fixed this as well.

Comment 5

[RuCla]

Please change status:

The error occurs again in last build (20060306). Example:
Previous declared event starts tommorrow at 17.30 and did not fire today at 18.00.

Comment 6

[RuCla]

Sorrry I mismatched build date: It is 20060304

Comment 7

[Michiel van Leeuwen (email: mvl+moz@)]

Please give more specific steps to reproduce. From your comment, I don't see a problem. Why would an alarm for an event tomorrow fire today?

Comment 8

[RuCla]

I used the option remind 1 day before event begins

Comment 9

[Joey Minta]

(In reply to comment #8)
> I used the option remind 1 day before event begins
> 
Please, as Michiel said, try and give some steps to reproduce.  Also, if you launch Sunbird with the -console option, there should be information about why Sunbird chose not to fire the alarm in the console.  That information would also be helpful in debugging.

Comment 10

[RuCla]

OK.
I have created an event which starts today at 17:30. In this event I have used the option "alarm". In this option I have selected "custom...". In the combobox I have selected "1 day before". So I suppose that the alarm should fire yesterday at 17:30 and later. Am I wrong? 

Comment 11

[Joey Minta]

(In reply to comment #10)
> OK.
> I have created an event which starts today at 17:30. In this event I have used
> the option "alarm". In this option I have selected "custom...". In the combobox
> I have selected "1 day before". So I suppose that the alarm should fire
> yesterday at 17:30 and later. Am I wrong? 
> 
I have created the same event, and it does fire the alarm immediately, which is why I really need/want the console information about why it chose not to fire the alarm.

Comment 12

[RuCla]

This is what I get from the console:
Error: document.styleSheets[i] has no properties
Source File: chrome://calendar/content/calendarManagement.js
Line: 262

Comment 13

[Joey Minta]

(In reply to comment #12)
> This is what I get from the console:
> Error: document.styleSheets[i] has no properties
> Source File: chrome://calendar/content/calendarManagement.js
> Line: 262
> 
Well, that's not the console I was talking about, but it helps.  You need to run Sunbird with the -console option, from the command-line.  Look for a line that says something like "***Starting calendar alarm service".  My guess is that because of this error, the alarm service is never getting started, and hence, no alarms are firing.  More directly, this error is the cause of bug 329424, so we should solve that one first and I bet it will fix things here.

Comment 14

[Worcester12345]

2/21/2006 version opened earlier and a past (passed?) event never fired. I installed a nightly build earlier this morning, and it fired on start of the program. Good job, and thanks.

Comment 15

[RuCla]

In the latest nighty everything works

Comment 16

[Damian Szczepanik]

verified with
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060914 Calendar/0.3a2+