303513 - Calender doesn't Show after Install

Status: RESOLVED WORKSFORME

(Calendar :: Lightning Only, defect)

Description

[Roland Schuller]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050719 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050719 Firefox/1.0+

I installed lightning.xpi (471KB) latest trunk
(ftp://ftp.mozilla.org/pub/mozilla.org/calendar/lightning/nightly/latest-trunk/windows-xpi/)
in Thunderbird 1.0.6 and DeerPark A2
After Installing restarted Thunderbird.
But i do not see any calendar, no Menu Entry and no Icon. Where is it?
No Error Message during Install.
I had the normal Calendar Installed bevore but removed it. Dont know if this helps?
What other Info do you need?

Reproducible: Always

Comment 1

[John Gaunt (redfive)]

Just tried to install a lightning that I built with t-bird (pulled today at
noon) on a fresh install of Deer Park A2. Tried in 2 different profiles that
both had extensions install in a previous version of FFox (1.0.6 I believe). I
got nothing related to Calendar in either of them.

I have successfully installed the lightning pointed to above (on the 5th, so
probably one day later therefore a new build) in the A2 of t-bird and I have
also pulled and built t-bird w/lightning today and successfully installed there.

Comment 2

[John Gaunt (redfive)]

I see an error in the js console on startup of DPA2 after installing Lightning:

Error: [Exception... "Invalid ClassID or ContractID"  nsresult: "0x80570017
(NS_ERROR_XPC_BAD_CID)"  location: "JS frame ::
file:///C:/Documents%20and%20Settings/redfive/Application%20Data/Mozilla/Firefox/Profiles/jhf4xw25.deer-park-a2/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calItemModule.js
:: initBaseComponent :: line 65"  data: no]
Source File:
file:///C:/Documents%20and%20Settings/redfive/Application%20Data/Mozilla/Firefox/Profiles/jhf4xw25.deer-park-a2/extensions/%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D/components/calItemModule.js
Line: 65

Checking the install files to make sure the ID for deer park is correct

Comment 3

[John Gaunt (redfive)]

It's not the deer park CID, but the CID for

const kCalRecurrenceRuleContractID = "@mozilla.org/calendar/recurrence-rule;1"; 

that seems to be causing the problem. Not sure why it works in t-bird but not in
ffox, somehow the file that defines this seems to not be getting loaded.

Comment 4

[John Gaunt (redfive)]

Attachment: nspr log of just the calendar stuff

Attaching a file that shows we try to get at Calendar/Event,
Calendar/Recurrence-rule, and calendar/alarm-service before a call to register
them is made.

Not sure why these 3 classes are getting skipped in the startup registration.

Comment 5

[Dan Mosedale (:dmosedale, :dmose)]

A snippet from stderr when attempting to install a nightly lightning into a CVS
trunk debug build:

nsNativeComponentLoader: autoregistering succeeded
nsNativeComponentLoader: registering deferred (0)
nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: SelfRegisterDll(calbscmp.dll) Load FAILED with error:
Unknown error
*** Registering mozStorageModule components (all right -- a generic module!)
nsNativeComponentLoader: SelfRegisterDll(webdav.dll) Load FAILED with error:
Unknown error
nsNativeComponentLoader: SelfRegisterDll(xmlextras.dll) Load FAILED with error:
Unknown error
nsNativeComponentLoader: autoregistering succeeded

Now in the case I'm trying, I'm loading a nightly from VC++ into a MinGW build,
which is almost certainly the problem here.  However, I'm wondering if the
problem that folks have been reporting could be similar: perhaps an impedence
mismatch between lightning components which have been built with --enable-debug,
and therefore have a different nsCOMPtr implemenation and nightly thunderbird
builds which are not built with debug.

Comment 6

[Dan Mosedale (:dmosedale, :dmose)]

Chase: I seem to recall that the Sunbird & Lightning build machine uses a
mozconfig that builds with --enable-debug.  Is my recollection correct?

Comment 7

[Chase Phillips]

(In reply to comment #6)
> Chase: I seem to recall that the Sunbird & Lightning build machine uses a
> mozconfig that builds with --enable-debug.  Is my recollection correct?

The initial mozconfigs had --enable-debug/--disable-optimize.  A bug was filed a
couple of weeks ago on Sunbird and Lightning to change that to
--disable-debug/--enable-optimize which I fixed.  The builds are currently
running with the latter.

Comment 8

[Mike Shaver (:shaver emeritus)]

Unfortunately, I do not have cycles to work on Calendar stuff these days (just as it's getting to the good part!), so I am a bad owner for these bugs.  To delete the tragically-large chunk of bugspam, search for gregorianabdication.

Comment 9

[Stefan Sitter [:ssitter]]

I have not seen reports of this error for a while now. I do not see this error with my own debug and release builds and with the official nightly builds. Probably fixed with the changes from bug 301973 and bug 314834. --> Resolving WFM.

Roland: If you still see this error with a recent Lightning build please reopen the bug.