Closed Bug 365599 Opened 18 years ago Closed 17 years ago

Snoozing alarm for 1 day dismisses alarm

Categories

(Calendar :: Alarms, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bitsrm, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
Build Identifier: Sunbird 0.3

After an alarm has fired and is displayed in the Alarms window, snoozing it for "1 day" causes it to not fire again after 1 day has elapsed i.e. it has been dismissed.

Reproducible: Always

Steps to Reproduce:
1. Create an alarm. Wait for it to fire.
2. Snooze for 1 day.
3. After 1 day it does not fire.
Actual Results:  
Alarm did not fire fire after 1 day.

Expected Results:  
Alarm should have fired after 1 day.
I could not confirm this with Build 2007010305. The snoozed alarm fired after one day as soon as I opened the calendar Program.

Reporter, have you tried the latest nightly build?
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12)
> Gecko/20050915
> Build Identifier: Sunbird 0.3
> 
> After an alarm has fired and is displayed in the Alarms window, snoozing it for
> "1 day" causes it to not fire again after 1 day has elapsed i.e. it has been
> dismissed.
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1. Create an alarm. Wait for it to fire.
> 2. Snooze for 1 day.
> 3. After 1 day it does not fire.
> Actual Results:  
> Alarm did not fire fire after 1 day.
> 
> Expected Results:  
> Alarm should have fired after 1 day.
> 

(In reply to comment #1)
> I could not confirm this with Build 2007010305. The snoozed alarm fired after
> one day as soon as I opened the calendar Program.
> 
> Reporter, have you tried the latest nightly build?
> 

I have not tried the latest nightly build.  The only version I have installed is the newest fully released version i.e. 0.3.
Please try the latest nightly from 

ftp://ftp.mozilla.org/pub/mozilla.org/calendar/sunbird/nightly/latest-trunk

and check if this Problem still shows up.
Mmm, let's see: 

Event with Alarm set for 15 minutes before:
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT15M
DESCRIPTION:Mozilla Alarm: New Event
ACTION:DISPLAY
END:VALARM

Event with snoozed alarm (5 minutes snooze is working)
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-PT15M
X-MOZ-LASTACK:20070312T172637Z
DESCRIPTION:Mozilla Alarm: New Event
ACTION:DISPLAY
END:VALARM

Now for one day: alarm set:
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-P1D
DESCRIPTION:Mozilla Alarm: New Event
ACTION:DISPLAY
END:VALARM

and after snoozing:
BEGIN:VALARM
TRIGGER;VALUE=DURATION:-P1D
X-MOZ-LASTACK:20070312T173238Z
DESCRIPTION:Mozilla Alarm: New Event
ACTION:DISPLAY
END:VALARM

Get back to you tomorrow, can't see why snoozing for one day wouldn't work for now...
I can't confirm this either, the alarm fired as it should... mark as WFM as we haven't heard from reporter in two months?
Reporter, feel free to re-open this bug if you still see the problem and please provide more information about your calendar (i.e. timezone settings, ICS export of calendar, is your computer in sleep mode while Sunbird is open?).
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.