Closed
Bug 424871
Opened 16 years ago
Closed 16 years ago
Calendar reminders don't cease after event has passed and was dismissed.
Categories
(Calendar :: Alarms, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 389251
People
(Reporter: acugnini, Unassigned)
Details
Attachments
(1 file)
1.35 KB,
text/plain
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; Windows-Media-Player/10.00.00.3990; .NET CLR 2.0.50727) Build Identifier: 2.0.0.12 (20080213) Rmeinders from a past event continue to pop up, even after reminder has been cleared. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Reporter | ||
Updated•16 years ago
|
Keywords: helpwanted
Comment 1•16 years ago
|
||
Please post the following information, so that we can try to reproduce the bug: - version of Lightning or Sunbird that you are using - .ics export file of the event that continues to pop up
Severity: major → normal
Keywords: helpwanted
Reporter | ||
Comment 2•16 years ago
|
||
Reporter | ||
Comment 3•16 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.8pre) Gecko/20071023 Sunbird/0.7
Comment 4•16 years ago
|
||
Aldo, please try this out with a current nightly linked from this article http://weblogs.mozillazine.org/calendar/2008/03/08_rc2_is_stuck.html There have been quite some fixes for the alarm system since 0.7, so this may already be fixed.
Reporter | ||
Comment 5•16 years ago
|
||
I downloaded 0.8, and it still has the problem. Here is what happens: as soon as I dismiss the reminder, it creates a new reminder (in the pop up window) of the same event at the same time. Thus, the reminders are never cleared.
Updated•16 years ago
|
Attachment #311480 -
Attachment mime type: application/octet-stream → text/plain
Comment 6•16 years ago
|
||
The attached .ics file contains a repeating event series without alarm and only one occurrence of that repeating series with an alarm set -> same as Bug 389251.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•