Closed
Bug 243144
Opened 20 years ago
Closed 18 years ago
Editing any event causes all alarms to go off
Categories
(Calendar :: Alarms, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 355755
People
(Reporter: batkiwi, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040407 Mozilla Sunbird/0.1.1+ I'm using a calendar which also publishes to a webdav server (apache 2 on fedora). If I create a new event, regardless of whether or not it has an alarm, all of my old alarms are triggered. Reproducible: Always Steps to Reproduce: 1. Use that calendar posted in the link field 2. Add a new event Actual Results: All old alarms go off again. Click ack on each one, follow steps again, same thing happens!! Expected Results: Not redone old alarms. My best guess is that it's reloading the alarms every time it saves or loads. I don't know if it's because I'm doing a local folder and webdav (with publish on each change checked) but it could be. This makes alarms useless, and I've had to turn them off.
Comment 1•20 years ago
|
||
Do you have the "auto-refresh" option set on the remorte calendar? If so, then it fetches a fresh calendat from your WebDAV server when you add the new event. It's most likely the refresh that causes your old alarms to go off. See bug 212076 about that. If so, this should probabely be marked as duplicate.
Comment 2•20 years ago
|
||
Reporter, Would you please try to reproduce this bug using the latest builds? Thanks
Comment 3•20 years ago
|
||
I have the same issue with reoccuring alarms when working of a remote server. This behaviour is under Windows 2000 and Debian. Sunbird stand-alone RC2
Comment 4•19 years ago
|
||
> Steps to Reproduce:
> 1. Use that calendar posted in the link field
> 2. Add a new event
>
> Actual Results:
> All old alarms go off again. Click ack on each one, follow steps again, same
> thing happens!!
WFM on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050812
Mozilla Sunbird/0.2+
Comment 5•19 years ago
|
||
Could be an issue with not having write access to the calendar, so the alarm acks weren't being saved. As far as I know, we don't yet have that problem sorted out, so I'm going to leave this one sitting here until our alarm support is back in better shape.
Updated•19 years ago
|
QA Contact: gurganbl → general
Comment 6•18 years ago
|
||
Reassigning all automatically assigned bugs from Mostafa to nobody@m.o Bugspam filter: TorontoMostafaMove
Assignee: mostafah → nobody
Comment 7•18 years ago
|
||
I cannot confirm it with Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061201 Calendar/0.4a1 But something is wrong with test calendar because it is in read only mode and generates a lot of errors in console. When I try to delete an event I can see these errors: Error: [Exception... "'<error>' when calling method: [calICalendar::deleteItem]" nsresult: "0x804a0002 (<unknown>)" location: "JS frame :: chrome://calendar/content/calendar-item-editing.js :: anonymous :: line 325" data: no] Source File: chrome://calendar/content/calendar-item-editing.js Line: 325 Error: [Exception... "'<error>' when calling method: [calICalendar::deleteItem]" nsresult: "0x804a0002 (<unknown>)" location: "JS frame :: chrome://calendar/content/calendar-item-editing.js :: anonymous :: line 325" data: no] Source File: chrome://calendar/content/calendar-item-editing.js Line: 325 Error: uncaught exception: [Exception... "'<error>' when calling method: [calICalendar::deleteItem]" nsresult: "0x804a0002 (<unknown>)" location: "JS frame :: chrome://calendar/content/calendar-item-editing.js :: anonymous :: line 325" data: no]
Comment 8•18 years ago
|
||
(In reply to comment #7) > But something is wrong with test calendar because it is in read only mode and > generates a lot of errors in console. When I try to delete an event I can see > these errors: This is intended because the calendar is read-only. The error thrown is CAL_IS_READONLY, see Bug 313640.
Updated•18 years ago
|
Component: General → Alarms
QA Contact: general → alarms
Comment 9•18 years ago
|
||
so can we close this issue, Omar B. can not reproduce it and errors are intended so I guess WFM?
Whiteboard: [qa discussion needed]
Comment 10•18 years ago
|
||
I believe the original issue in this bug was the same as the issue that was fixed in bug 212076. We do still have an issue with alarms and readonly remote calendars -- those alarms will pop up each time you start the Calendar -- this bug is being addressed in bug 355755. Because this bug has been designated as a "read-only" calendar problem, I'll dupe it against 355755.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•