Lightning calendar broken ever since 2.32 [SOLVED]

[mahdi1234]

Hi there,

I have a problem on linux machine, on W7 with Windows Lightning everything works fine, however on Linux (Gentoo x86) it stopped to work since 2.32.

Code: Select all

Seamokey 2.31 + Lightning 3.6b3 

User agent: Mozilla/5.0 (X11; Linux i686; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31
Build identifier: 20141202221108

with above everything's fine

Code: Select all

Seamokey 2.33 + Lightning 3.8b1 

User agent: Mozilla/5.0 (X11; Linux i686; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33
Build identifier: 20150308222504

with 2.33 I get below for every calendar item -

Code: Select all

Warning: Failed to parse item: BEGIN:VCALENDAR
PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN
VERSION:2.0
BEGIN:VTODO
CREATED:20130829T200425Z
LAST-MODIFIED:20150219T085758Z
DTSTAMP:20150219T085758Z
UID:09589969-ddf4-4296-be12-dc464fdb49a6
SUMMARY:xyz
X-MOZ-GENERATION:27
END:VTODO
END:VCALENDAR


Exception:[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [calIICSService.parseICS]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: resource://calendar/modules/calUtils.jsm -> file:///home/user/.mozilla/seamonkey/4w6fxvnj.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calIcsParser.js :: ip_parseString :: line 135"  data: no]
Warning: Failed to parse item: BEGIN:VCALENDAR

and for every todo -

Code: Select all

Calendar] Message: Error selecting non recurring todos by range
Connection Ready: true
Last DB Error Number: 100
Last DB Error Message: unknown error
Database File: /home/user/.mozilla/seamonkey/4w6fxvnj.default/calendar-data/local.sqlite
Last DB Statement: [object StatementJSHelper]
Last Statement param [range_start]: -9223372036854776000
Last Statement param [start_offset]: 0
Last Statement param [range_end]: 9223372036854776000
Last Statement param [end_offset]: 0
Last Statement param [cal_id]: 358fceb9-ab8c-4cf7-bf2d-ff28ae187375
Last Statement param [offline_journal]: null
Exception: [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:///home/user/.mozilla/seamonkey/4w6fxvnj.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calUtils.js :: _calIcalCreator/< :: line 17"  data: no]
1: [file:///home/user/.mozilla/seamonkey/4w6fxvnj.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calStorageCalendar.js:2414] cSC_logError
2: [file:///home/user/.mozilla/seamonkey/4w6fxvnj.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calStorageCalendar.js:883] cSC_getItems_
3: [file:///home/user/.mozilla/seamonkey/4w6fxvnj.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calStorageCalendar.js:660] cSC_getItems/<
4: [null:0] null

anyone else seen similar problem? I have tried disabling all other extensions, did not help either.

Would like to mention once again, when downgrading to Seamonkey 2.31 calendar works with the very same configuration.

thanks

[smsmith]

Is the calendar view basically blank? That's what I have been getting. Can't change the view from Month to Day or Week, either.

At one point I found this bug, which describes and has screenshots of the same thing I see, but it was duped as resolved in another bug, for a version meant for SM 2.34.
https://bugzilla.mozilla.org/show_bug.cgi?id=1136890

[mahdi1234]

Thanks, this looks quite the same problem as I'm having including timezone settings. Hopefully will work again in next version, will check once 2.34 beta is available.

[WaltS48]

Try Lightning 3.8b2

Lightning :: Versions :: Add-ons for Thunderbird

[mahdi1234]

Try Lightning 3.8b2

Lightning :: Versions :: Add-ons for Thunderbird

It doesn't work with 3.8b2, tried that this morning. It seems from the linked defects the problem is in the platform, not the extension, thus 2.34 needed.

[rsx11m]

Moving to Calendar.

[mahdi1234]

Ok, just read about setting calendar.icaljs to false, don't know if it worked before (3.8b1), but it definitely fixes my problem with 3.8b2 using this value.

[smsmith]

Is this just a temporary workaround that I need to remember to revert when SM 2.34 and Lightning 3.9 are released?

Moot point, because it changes nothing for me. In fact, calendar.icaljs has a default value of false and was already set that way. Even tried it in a never had Lightning installed profile.

[mahdi1234]

Looks like temoporary workaround based on this defect - https://bugzilla.mozilla.org/show_bug.cgi?id=1081534

MakeMyDay 2014-12-05 11:15:28 PST

@Philipp: I'll give it a try.

@rsx11m: to work around this, disable calendar.icaljs in the config editor. Once this is fixed, I will propose to backport this also to Aurora and Beta.

[rsteinmetz70112]

I jsust reied the "fix" calendar.icaljs to false, but it was already false so not joy.

[rsx11m]

Yeah, I remember that there was some confusion about the calendar.icaljs setting, but it should be switched off already by default (as was stated here) and thus shouldn't trigger the bug. The workaround was for 3.6, but 3.7 and 3.8 should have that fix already included based on the branch approvals. But bummer - they forgot to land it! Thus, it'll be fixed with 3.9, but won't help people running into the issue on 3.8 (but then, this may not be the cause of the problem you see after all).

[rsteinmetz70112]

Looking at Bugzilla people were still reporting the problem with reference to bug 1081534 which is listed as fixed in 3.9, however it appears that Seamonkey 34 will be delayed, leaving no reliably working version of Lightning for SeaMonkey 33.

[ndebord]

Looking at Bugzilla people were still reporting the problem with reference to bug 1081534 which is listed as fixed in 3.9, however it appears that Seamonkey 34 will be delayed, leaving no reliably working version of Lightning for SeaMonkey 33.

rsteinmetz70112,

PMFJI on your thread... same problem... my temporary solution was to go find SunBird 1.0b1 and use that until this gets resolved.

FWIW