I took a look using the test calendars and was able to reproduce this and get a stack trace (below). I'm out of time today, but will try again on Monday. It does look like fallout from bug 1546606. calCachedCalendar.js:346:23 onResult resource:///components/calCachedCalendar.js:346 completeCheckServerInfo resource:///modules/CalDavCalendar.jsm:1872 checkDavResourceType resource:///modules/CalDavCalendar.jsm:1474 (Async: promise callback) checkDavResourceType resource:///modules/CalDavCalendar.jsm:1458 replayChangesOn resource:///modules/CalDavCalendar.jsm:235 synchronize resource:///components/calCachedCalendar.js:363 downstreamRefresh resource:///components/calCachedCalendar.js:716 popItemQueue resource:///components/calCachedCalendar.js:616 onOperationComplete resource:///components/calCachedCalendar.js:658 notifyPureOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:515 notifyOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:534 getItems resource:///modules/CalStorageCalendar.jsm:838 playbackOfflineItems resource:///components/calCachedCalendar.js:663 popItemQueue resource:///components/calCachedCalendar.js:616 onOperationComplete resource:///components/calCachedCalendar.js:658 notifyPureOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:515 notifyOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:534 getItems resource:///modules/CalStorageCalendar.jsm:838 playbackOfflineItems resource:///components/calCachedCalendar.js:663 popItemQueue resource:///components/calCachedCalendar.js:616 onOperationComplete resource:///components/calCachedCalendar.js:658 notifyPureOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:515 notifyOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:534 getItems resource:///modules/CalStorageCalendar.jsm:838 playbackOfflineItems resource:///components/calCachedCalendar.js:663 refresh resource:///components/calCachedCalendar.js:707 registerCalendar resource:///modules/CalCalendarManager.jsm:265 doCreateCalendar chrome://calendar/content/calendarCreation.js:248 doCreateCalendar chrome://lightning/content/lightning-calendar-creation.js:20 doCreateCalendar chrome://lightning/content/caldav-lightning-calendar-creation.js:18 _fireEvent chrome://global/content/elements/wizard.js:483 advance chrome://global/content/elements/wizard.js:292 listeners chrome://global/content/elements/wizard.js:535 (Async: EventListener.handleEvent) connectedCallback chrome://global/content/elements/wizard.js:544 (Async: LifecycleConnectedCallback) <anonymous> chrome://global/content/elements/wizard.js:668 <anonymous> chrome://global/content/customElements.js:839 <anonymous> chrome://global/content/customElements.js:862 observe resource://gre/modules/CustomElementsListener.jsm:24
Bug 1630943 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I took a look using the test calendars and was able to reproduce this and get a stack trace (below). I'm out of time today, but will try again on Monday. It does look like fallout from bug 1546606. Edit: the following log is from doing a `console.trace()` right before the `cal.ERROR("[calCachedCalendar] replay action failed: "` in calCachedCalendar.js (which is the error Kai mentioned at the top of this bug). calCachedCalendar.js:346:23 onResult resource:///components/calCachedCalendar.js:346 completeCheckServerInfo resource:///modules/CalDavCalendar.jsm:1872 checkDavResourceType resource:///modules/CalDavCalendar.jsm:1474 (Async: promise callback) checkDavResourceType resource:///modules/CalDavCalendar.jsm:1458 replayChangesOn resource:///modules/CalDavCalendar.jsm:235 synchronize resource:///components/calCachedCalendar.js:363 downstreamRefresh resource:///components/calCachedCalendar.js:716 popItemQueue resource:///components/calCachedCalendar.js:616 onOperationComplete resource:///components/calCachedCalendar.js:658 notifyPureOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:515 notifyOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:534 getItems resource:///modules/CalStorageCalendar.jsm:838 playbackOfflineItems resource:///components/calCachedCalendar.js:663 popItemQueue resource:///components/calCachedCalendar.js:616 onOperationComplete resource:///components/calCachedCalendar.js:658 notifyPureOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:515 notifyOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:534 getItems resource:///modules/CalStorageCalendar.jsm:838 playbackOfflineItems resource:///components/calCachedCalendar.js:663 popItemQueue resource:///components/calCachedCalendar.js:616 onOperationComplete resource:///components/calCachedCalendar.js:658 notifyPureOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:515 notifyOperationComplete resource:///modules/calendar/utils/calProviderUtils.jsm:534 getItems resource:///modules/CalStorageCalendar.jsm:838 playbackOfflineItems resource:///components/calCachedCalendar.js:663 refresh resource:///components/calCachedCalendar.js:707 registerCalendar resource:///modules/CalCalendarManager.jsm:265 doCreateCalendar chrome://calendar/content/calendarCreation.js:248 doCreateCalendar chrome://lightning/content/lightning-calendar-creation.js:20 doCreateCalendar chrome://lightning/content/caldav-lightning-calendar-creation.js:18 _fireEvent chrome://global/content/elements/wizard.js:483 advance chrome://global/content/elements/wizard.js:292 listeners chrome://global/content/elements/wizard.js:535 (Async: EventListener.handleEvent) connectedCallback chrome://global/content/elements/wizard.js:544 (Async: LifecycleConnectedCallback) <anonymous> chrome://global/content/elements/wizard.js:668 <anonymous> chrome://global/content/customElements.js:839 <anonymous> chrome://global/content/customElements.js:862 observe resource://gre/modules/CustomElementsListener.jsm:24