CalDAV (davmail) no longer works; console shows error: [Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCCompo
Starting Thunderbird 77.0b2 CalDAV calendar in Lightning no longer works. No events are loaded and in the console the error message below shows up several times:
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]" nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)" location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 658" data: no] L10nRegistry.jsm:658:19
loadSync resource://gre/modules/L10nRegistry.jsm:658 fetchFile resource://gre/modules/L10nRegistry.jsm:573 generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:478 map self-hosted:240 generateResourceSetSync resource://gre/modules/L10nRegistry.jsm:473 generateResourceSetsForLocaleSync resource://gre/modules/L10nRegistry.jsm:415 next self-hosted:1099 generateBundlesSync resource://gre/modules/L10nRegistry.jsm:177 next self-hosted:1099 touchNext resource://gre/modules/Localization.jsm:167 regenerateBundles resource://gre/modules/Localization.jsm:552 activate resource://gre/modules/Localization.jsm:243 <anonymous> resource:///modules/calendar/calCalendarDeactivator.jsm:10 <anonymous> chrome://calendar/content/calendar-chrome-startup.js:25
Is there something I can do to fix this?
Opaite Mbohovái (3)
Try Beta three perhaps? Report a bug https://bugzilla.mozilla.org/home
Or if your not testing, perhaps just use the release version which is stable.
In the mean time it is beta 4 and the problem is till there. Though I guess the original post is rubbish and the reported error has nothing to do with the fact that Lightning + Davmail no longer work. But maybe the other error I get has something to do with CalDAV calendar not working:
TypeError: response.firstProps['D:supported-report-set'] is undefined CalDavCalendar.jsm:1521:13
I guess I will open a bug report than.
It seems others have already created a bug report for this 1649036