239766 - Installed completed but before Mozilla launched it reported 2 errors: (1) components /libxpical.so not a valid windows image; and (2) the procedure entry point ??1nsCString@@UAE@X2 could not be located in the dll xpcom.dll

Status: RESOLVED WORKSFORME

(SeaMonkey :: Installer, defect)

Description

[chancery]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7b) Gecko/20040316

Installed completed but before Mozilla launched it reported 2 errors: (1)
components /libxpical.so not a valid windows image; and (2) the procedure entry
point ??1nsCString@@UAE@X2 could not be located in the dll xpcom.dll

After I clicked okay, the browser started up as usual. 

Reproducible: Always
Steps to Reproduce:
1. removed using Windows uninstaller
2. download & install Mozilla v. 1.7b
3. installed & error messages appeared
4. goto 1. twice

Actual Results:  
same error messages. After clicking ok, Mozilla started up without a hitch.

Expected Results:  
Produced no error message and start up cleanly

Comment 1

[Benjamin Smedberg]

1) Where did you download this mozilla1.7b?
2) where did you get calendar?

calendar does not come with mozilla1.7b, and libxpical.so is a unix-style shared
library. I suspect you have something left over in your installation directory,
or are installing an incompatible calendar XPI.

Comment 2

[Danny Staple]

After installing Calendar extension into Thunderbird 0.6 on Windows XP SP 1, I
see this. 

It only appears the first time - but after this - the calendar extension pops up
errors - including one pointing me to 122860 (checking the installed components
and removing compreg.dat) - which then just leads to this error again.

I did not see this when I installed the same extension into Thunderbird 0.5.
May I therefore suggest changing the product for this bug to Calendar?

Comment 3

[OstGote!]

No response from reporter, old build. Please resolve this bug.

Comment 4

[:Gavin Sharp [email: [e-mail]]]

Related to bug 140188. Resolving as WFM, old build with no response.