User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-DE; rv:1.7.5) Gecko/20041108 Firefox/1.0 If you set alarm "before the task is due" it does only rarely work. It never works if you change the due time or alarm time of an existing event. A second alarm is never been sent. Reproducible: Always Steps to Reproduce: 1. Create Task with Start Date: Same Day 0:00 and End Date same day, some minutes in the future. Set an alarm to "1 Minute before the task is due" and "Email Alarm to email@example.com" 2. In General there will never occur any alarm. If it really occurs, change the End Date to some minutes in the future an leave the alarm settings to "1 Minute before the task is due" and "Email Alarm to firstname.lastname@example.org" 3. The second alarm is never sent. Actual Results: Nothing Expected Results: Give an alarm Calendar as Thunderbird Extension, Version calendar_windows_20041112.xpi Theme: qute_Nitpick_0.1.7.9
In the meantime I noticed that the alarms are not missing, they are just suppressed. When restart windows and open the calendar again I get all the missed alarms at once. Perhaps this is important: I used to use SunTray (http://users.dart.net.au/~srgeorg/). I uninstalled it some days ago as it crashed quite often but the missing-alarm-problem still exists.
Confirmed on Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8a5) Gecko/20041112 Mozilla Sunbird/0.2b. Creating a new task starting today at 00:00 and ending later this day is always displayed in red even the actual time is still before the due time. An alarm configured before the due time does not work. A new task starting yesterday and ending later today is correctly displayed in blue and also alarms are working well. A new task starting today and ending tomorrow 15:00 is correctly displayed in green but an alarm configured '1 day before task is due' does not work as expected at 15:00.
I see... I think it should be possible to set an alarm for a task starting today at 00:00 and ending later this day. Or at least warn the user if it sets an alarm that won't work.
Additional Comment concerning comment #2: There is another problem left: The alarms are not suppressed, they are just not triggered in time. This happened today: I had a Task beginning 25.11.2004 at 10:00 and ending 23.06.2005 at 11:10. The alarm should be "1 Day before the task starts". My calendar war running all day on 24.11.2004 an there was no alarm. When I booted Windows tomorrow at 9:30 and startet the calendar the alarm came, one day too late. It is not that the alarms are not happening at all, they are somehow "blocked" or "kept back" and are all executed after the next reboot of windows.
Alarms were overhauled in nightly builds a few weeks back and I'm fairly sure that we got this fixed. It'd be great if someone could download a nightly build and confirm.
Reassigning all automatically assigned bugs from Mostafa to email@example.com Bugspam filter: TorontoMostafaMove