Closed Bug 864012 Opened 12 years ago Closed 2 years ago

Unable to dismiss Alarms using Google Calendar

Categories

(Calendar :: Alarms, defect)

Lightning 1.9.1
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mail, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 Build ID: 20130329030832 Steps to reproduce: Add a Google Calendar using the private ICAL URL (Offline Support unchecked) Edit the properties and disable Read Only, if checked When alarms appear, click Dismiss All Actual results: Nothing visible (window stays open) Error console shows: Error: '<error>' when calling method: [calICalendar::modifyItem] Source File: resource://calendar/modules/calUtils.jsm -> file:///home/jan/.thunderbird/yiyyagme.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calAlarmService.js Line: 207 line 207 is: return newParent.calendar.modifyItem(newParent, oldParent, null); Window "An error has occurred" shows, with error MODIFICATION_FAILED Expected results: Alarm window should disappear and alarm be dismissed Or - at least - some kind of usable error message should be found somewhere.
As reported on #667070, I have the same problem. But I doesn't get an error.
I onl get the error the first time. Then, the calendar gets set to Read-Only, and Dismissing is completely impossible (there is a bug report for that). To see the error again, I have to disable the Read-Only checkbox first.
Bug 667070 seems to be something different. It claims that alarms are deleted unexpectedly. My problem is that I can *not* dismiss the alarm. Also, I use ICAL instead of WebDAV (Google no longer supports WebDAV). When I used WebDAV, the problem did not occur.
Severity: normal → S3

Reporter,

Does this issue still reproduce for you when using version 102.6.1 or newer?
If yes, please provide additional details (type of calendar, etc).
Thanks

Whiteboard: [closeme 2023-01-20]

Sorry, I don't use Thunderbird at the moment, so I can't test it. As it ten years ago and did not receive any comments from someone else, I guess it's safe to close though.

Resolved per whiteboard and Comment 5

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2023-01-20]
You need to log in before you can comment on or make changes to this bug.