672621 - cannot dismiss or snooze tasks in lightning

Status: RESOLVED DUPLICATE of bug 356002

(Calendar :: Alarms, defect)

Description

[[e-mail]]

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

Steps to reproduce:

tried to both sooze and dismiss task when reminders appear. 


Actual results:

The noperation failed and when I closed the window to shut down the reminders error message appears "cannot resolve...the rest I have forgotten


Expected results:

the tasks should have either dismissed or snoozed

Comment 1

[Philipp Kewisch [:Fallen][☁️📆]]

Could you paste the exact error message?

Comment 2

[Martin Schröder [:mschroeder]]

Brian, is this still an issue using the recently released Lightning 1.0 (compatible with Thunderbird 8)?

Comment 3

[Martin Schröder [:mschroeder]]

(In reply to Martin Schröder [:mschroeder] from comment #2)
> Brian, is this still an issue using the recently released Lightning 1.0
> (compatible with Thunderbird 8)?

Brian confirmed this issue in Lightning 1.0 (Thunderbird 8) via email.

Brian, can you post a more detailed error message and the kind of calendar you use?

Comment 4

[Jim Skorey]

I have the same problem.  I cannot snooze a repetive event  receive an error msg.

Comment 5

[David B Teague]

When alarm is shown, snooze for any period of time fails because "cannot write to Lighening Home". I'll copy and paste the error message when it happens again. This is a sorely needed fix as I depend on this calendar.

Comment 6

[David von Oheimb]

With Lightning 1.4 on Thunderbird 12.0.1, snoozing or dismissing events does not work for me either (no effect). Maybe it is related to the following JavaScript errors:

Warning: There has been an error reading data for calendar: dax. It has been placed in read-only mode, since changes to this calendar will likely result in data-loss.  You may change this setting by choosing 'Edit Calendar'. Error code: DAV_PUT_ERROR. Description: Publishing the calendar file failed
Status code: 0

Error: An error occurred when writing to the calendar dax! Error code: MODIFICATION_FAILED. Description: 
Source File: resource://calendar/modules/calUtils.jsm -> file:///Users/ [...] /extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js
Line: 1108

Error: Components.classes['@mozilla.org/extensions/manager;1'] is undefined
Source File: chrome://local_install/content/local_install.js
Line: 1689

Comment 7

[Matthew Mecca [:mmecca]]

(In reply to David von Oheimb from comment #6)
> Warning: There has been an error reading data for calendar: dax. It has been
> placed in read-only mode, since changes to this calendar will likely result
> in data-loss.  You may change this setting by choosing 'Edit Calendar'.
> Error code: DAV_PUT_ERROR. Description: Publishing the calendar file failed
> Status code: 0

That looks like the source of the problem - an error is occurring when the calendar is written to, and the calendar is being set to read-only because of it. The alarms can't be dismissed at that point - see Bug 356002.

Are you able to make any changes to that calendar at all, and if not were you able to before upgrading to Lightning 1.4? If so I would suggest filing a new bug for that. If the alarms are getting in the way troubleshooting the calendar issue you can temporarily disable them for that calendar by double-clicking on the calendar's name in the calendar list, and un-checking the "Show Reminders" box.

Comment 8

[David von Oheimb]

Thanks Matthew for your quick and constructive response.

Indeed, my calendar had become read-only (due to some network error?), so Bug 356002 applies. Yes, I was not able to do other change to the calendar until I re-started Thunderbird to recover from the error putting the calendar to read-only. I can't recall exactly the behavior in earlier Lightning versions, but I think it was the same.

In any case, if dismiss or snooze fails for whatever reason, a to-the-point info should be given to the user (e.g., "write to calendar failed") rather than just doing nothing and letting the user wonder why there is no effect.

Comment 9

[Matthew Mecca [:mmecca]]

Closing this as duplicate of Bug 356002, if any reporters continue to experience this issue and do not feel it is related to the calendar being temporarily or permanently set to read-only, please feel free to file a new bug, preferably with the detailed error messages from the error console.