MozillaZine

Problem with Lightning 2.6

For discussing the Mozilla Calendar, Sunbird and Lightning projects.
wolpi
 
Posts: 5
Joined: September 20th, 2013, 9:27 am

Post Posted September 20th, 2013, 9:41 am

Hello,

I've got a problem with Lightning 2.6 (+ Seamonkey 2.21). I'm using a CalDav connection to a Keiro Connect Server which worked perfectly until I updated Seamonkey and Lightning to the recent version. I didn't change my settings and also tried to delete and add the calender again - but there is no use: it doesn't work. It also seems that the error occurs on every http-address. Whenever I try to connect to a CalDav Server I immediately get following errors:

Fehler: NS_ERROR_FILE_NOT_FOUND: Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXPCComponents_Utils.import]
Quelldatei: resource://calendar/modules/OAuth2.jsm
Zeile: 12

Fehler: [Exception... "Component returned failure code: 0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE) [nsIJSCID.createInstance]" nsresult: "0x80570015 (NS_ERROR_XPC_CI_RETURNED_FAILURE)" location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///D:/Seamonkey/profile/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 474" data: no]

What can I do now?

Thank you very much in advance

ssitter

User avatar
 
Posts: 2495
Joined: October 19th, 2007, 12:24 am
Location: Germany

Post Posted September 20th, 2013, 2:47 pm

Looks like CalDAV calendar provider is not working in SeaMonkey 2.21 at all because it depends on a file that is only available in Thunderbird 24. I filed Bug 919018.

wolpi
 
Posts: 5
Joined: September 20th, 2013, 9:27 am

Post Posted September 21st, 2013, 12:05 am

Thank you very much for reporting the bug.

ssitter

User avatar
 
Posts: 2495
Joined: October 19th, 2007, 12:24 am
Location: Germany

Post Posted September 25th, 2013, 12:42 pm

Looks like there won't be any action. The problem ought to be fixed in the next SeaMonkey 2.22 release. I think currently you can only switch back to SeaMonkey 2.20 + Lightning 2.5 Beta or jump to SeaMonkey 2.22 Beta + Lightning 2.7 Beta when available.

wolpi
 
Posts: 5
Joined: September 20th, 2013, 9:27 am

Post Posted September 29th, 2013, 10:27 am

Thank you for the hint. I read in bugzilla about a workaround and added the http.jsm to omni.ja manually. It's working now.

Return to Calendar


Who is online

Users browsing this forum: No registered users and 3 guests