Closed
Bug 597908
Opened 14 years ago
Closed 14 years ago
Lightning doesn't work (blank display). Error console says: Components.classes['@mozilla.org/calendar/datetime;1'] is undefined
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: tonymec, Unassigned)
Details
(Keywords: regression, useless-UI)
Attachments
(5 files)
Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100919 Firefox/4.0b7pre SeaMonkey/2.1b1pre
See attached screenshot.
- None of my calendars and events are visible.
- "New calendar" does nothing AFAICT (the new-calendar dialog doesn't even pop up)
- The grid header says "Day" but the grid itself is a 6-row month or multiweek grid
- My usual grid is a 5-row multiweek.
Until yesterday I was using the last SeaMonkey and Lightning trunk builds from before the XPCOM bustage.
Yesterday's Lightning worked with yesterday's SeaMonkey in a fresh profile. Today's versions don't work in my usual profile, even after disabling every single extension (including built-in extensions) other than lightning and gdata-provider.
Error console says:
Error: Components.classes['@mozilla.org/calendar/datetime;1'] is undefined
Source File: chrome://calendar/content/calUtils.js
Line: 75
Is this a Toolkit::AddonsManager bug? A Calendar::SeaMonkeyIntegration bug? A Calendar::CalendarViews bug? Something else? I don't know. I'm at the end of my wits, with a headache for trying to solve this problem, and I'm going to bed (in a few minutes it'll be 2AM my time). See you tomorrow.
Comment 1•14 years ago
|
||
Might be the result of Bug 533038, see Lightning Bug 593058.
Comment 2•14 years ago
|
||
Tony, could you check if adding <em:unpack>true</em:unpack> to the install.rdf fixes the issue?
Reporter | ||
Comment 3•14 years ago
|
||
(In reply to comment #2)
> Tony, could you check if adding <em:unpack>true</em:unpack> to the install.rdf
> fixes the issue?
ATM I'm doing it for Lightning only, please say if gdata-provider needs it too.
I'm adding that line just before the closing tag for <Description about="urn:mozilla:install-manifest">, after the <em:targetPlatform> element (hoping that's the right place, as I don't know the structure of install.rdf). Repack, click the link in the file:/// view of the directory... "Lightning will be updated after you restart SeaMonkey"... as soon as this comment is posted, I'll restart, with all my tabs the restart can be slowish, please bear with me...
Reporter | ||
Comment 4•14 years ago
|
||
The restart crashed at startup, bp-4408392b-c97b-4720-a0d1-15fed2100920 so I'm typing this in safe mode. Now I'll disable Lightning, reenable my "cannot-live-without" extensions, and unwrap Sunbird "Gecko/20100526 Calendar/1.0b2pre" for the time being.
Reporter | ||
Comment 5•14 years ago
|
||
Reporter | ||
Comment 6•14 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100920 Firefox/4.0b7pre SeaMonkey/2.1b1pre - Build ID: 20100920010446
No change with Sm + L + GDP nightlies from Sep.20:
- crash at startup with <em:unpack>true</em:unpack> (except in Safe Mode)
- otherwise, Lightning doesn't work
I'm attaching 4 addons-related files, copied while SeaMonkey is running.
Reporter | ||
Comment 7•14 years ago
|
||
Reporter | ||
Comment 8•14 years ago
|
||
Reporter | ||
Comment 9•14 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100924 Firefox/4.0b7pre SeaMonkey/2.1b1pre - Build ID: 20100924025624
With this nightly, and the latest hourlies of lightning and gdata-provider, symptoms have changed:
- crash at first startup, bp-18fe6ef1-d47a-4b3a-9eb0-0a6ed2100924
- Lightning works on restart from "Restart SeaMonkey" on Breakpad dialog
- Calendar list is not displayed in Lightning left pane, even though it is ticked in the "View => Calendar" menu: this means I cannot enable/disable calendars or view their Properties (except maybe in about:config)
- Error (presumably from gdata-provider) for my only Google calendar, as follows:
An error has occurred
---------------------
An error was encountered preparing the calendar located at http://www.google.com/calendar/ical/<censored>/basic.ics for use. It will not be available.
[ Details… ]
Error code: 0x80570015
Description: [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:///root/.mozilla/seamonkey/nexrdon9.default/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/calendar-js/calCalendarManager.js :: cmgr_createCalendar :: line 580" data: no]
Can all this be handled in the present bug, or should I file a followup bug or two:
- for the missing Calendar list?
- for the Google calendar problem?
Reporter | ||
Comment 10•14 years ago
|
||
P.S. In comment #9, Lightning and gdata-provider XPIs were from ftp://ftp.mozilla.org/pub/mozilla.org/calendar/tinderbox-builds/comm-central/linux-xpi-linux/1285320209/ dated 24SEP10 02:44
Reporter | ||
Comment 11•14 years ago
|
||
On third startup, after one more crash, bp-a8420610-7a56-456d-8b45-0b5b82100924 , the calendar list is displayed, and also the "Show…" radiobutton-list, but the latter is all greyed-out, and the events list (above the grid) shows up blank.
Same google-calendar error as in comment #9; after dismissing it, I tried to enable that calendar manually (nothing happened) then to view its Properties (crash, bp-af7ab74f-3f87-40d9-a752-d459b2100924 ).
Reporter | ||
Comment 12•14 years ago
|
||
One more: bp-b1bc878a-948c-4f2a-87f4-9d30c2100924
This is too much, I'm disabling L+GDP, at least for today.
Reporter | ||
Comment 13•14 years ago
|
||
Mozilla/5.0 (X11; Linux i686; rv:2.0b7pre) Gecko/20100925 Firefox/4.0b7pre SeaMonkey/2.1b1pre - Build ID: 20100925010142
I'm closing this bug WFM: Lightning now works -- after a fashion. I may report followup bugs for the problems listed in comment #9 if I find how to formulate them. The startup crash is bug 599637.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•