1240614 - Lightning cannot dismiss calendar notifications for Zimbra calendars (uncaught exception 2152333314)

Status: UNCONFIRMED

(Calendar :: Alarms, defect)

Description

[Ben Lerner]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030

Steps to reproduce:

I have a Zimbra calendar with a recurring event (for what it's worth, the recurrence is weekly, two days a week) with an alarm.  The alarm will display in Thunderbird fine, but dismissing it gives an error.  It appears to be a different trace than in bug 432540, and we have a far more recent version of Zimbra (v8.6.0) than in that bug (v5.0.6), so I think this is a new problem.


Actual results:

The alarm window will not display, and in the console I get three errors:

Timestamp: 1/18/2016 4:13:46 PM
Error: uncaught exception: 2152333314

Timestamp: 1/18/2016 4:13:46 PM
Error: : <error>'<error>' when calling method: [calICalendar::modifyItem]
Source File: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/Ben/AppData/Roaming/Thunderbird/Profiles/481p2bn0.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calAlarmService.js
Line: 200

Timestamp: 1/18/2016 4:13:46 PM
Error: : <error>'<error>' when calling method: [calICalendar::modifyItem]
Source File: resource://calendar/modules/calUtils.jsm -> file:///C:/Users/Ben/AppData/Roaming/Thunderbird/Profiles/481p2bn0.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calAlarmService.js
Line: 200

I don't know whether the duplicated line is because there are two alarms (for the previous two instances of the same recurring event) that I can't dismiss, though it seems likely.  I was able to dismiss the alarms by going into Zimbra and deleting the alarm entirely from the event, then resynchronizing with Lightning.  But that's a rather drastic solution...

Comment 1

[[:MakeMyDay]]

Can you please enable calendar.debug.log and calendar.debug.log.verbose in the config editor, check yor log again for further details and report back?

Comment 2

[Ben Lerner]

Both flags are already set to true (was using them to debug a timezone problem before, and never turned them off).  My exact procedure, given that I have those two flags set, was to clear the error console, then click the dismiss button on the alarms window.  Only the messages above were logged.  Each time I clicked dismiss, I got another set of those messages.

Comment 3

[Matthew Mecca [:mmecca]]

(In reply to Ben Lerner from comment #0)
> Error: uncaught exception: 2152333314

That error code corresponds to CAL_IS_READONLY. Is the calendar configured to be writeable from Lightning?

Comment 4

[Ben Lerner]

Wellllllll that's embarrassing.  I don't recall marking the calendar as readonly, though somehow it appears to be.  I'll try flipping that flag, restoring the alarms, and checking again tomorrow (when the next recurrence recurs).

If that turns out to be the culprit, is there a cleaner UI for informing a clueless user (like I appear to be) that you can't dismiss alarms on readonly calendars?

Comment 5

[Ben Lerner]

Seems to have been my mistake in making the calendar readonly.  Apologies for a bogus bug...  But the second part of my question above remains -- is there any UI I missed that would've informed me that this exception number was because of a readonly calendar?