Closed Bug 435057 Opened 17 years ago Closed 17 years ago

Cannot dismiss alarm of a rescheduled instance of a recurring meeting

Categories

(Calendar :: Alarms, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 389251

People

(Reporter: bernard.desruisseaux, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080421 Lightning/0.9pre Thunderbird/2.0.0.14 I cannot dismiss the alarm of a rescheduled instance of a recurring meeting. When I click Dismiss or Dismiss All the alarm goes off again immediately. Reproducible: Always Steps to Reproduce: 1. Create recurring meeting (e.g., weekly on Monday at 2:00 pm for 5 weeks) with no reminders. 2. Modify 2nd instance to occur on Monday at 3:00 pm and set the reminder to "15 minutes before" Actual Results: 15 minutes before the meeting the alarm should go off. Click Dismiss or Dismiss All and notice that the alarm will go off again. Expected Results: Alarm should be dismissed once for good. I found this issue while using Mozilla Lightning against Oracle's CalDAV Server. After the alarm is dismissed Mozilla sends an updated copy of the meeting to the CalDAV server, but the reschedule instance still contains the original VALARM component (i.e., the bug): BEGIN:VALARM TRIGGER;VALUE=DURATION:-PT15M DESCRIPTION:Mozilla Alarm: [+] Test Alarm ACTION:DISPLAY END:VALARM Lightning should actually send the meeting with no VALARM component, or at a minimum specify the X-MOZ-LASTACK property as done for single instance meetings. This bug is related to bug 379392 and bug 397030 but I believe is a separate issue (i.e., specific to rescheduled instance of a recurring meeting)
Sounds like a duplicate of Bug 389251.
Yes it is.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.