381079 - "Failed to load XPCOM component: ...\seamonkey\components\XPCOMUtils.jsm"

Status: VERIFIED INVALID

(SeaMonkey :: General, defect)

Description

[Serge Gautherie (:sgautherie)]

Moved from bug 380913.

{{
Regressed between

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070515
SeaMonkey/1.5a] (nightly) (W2Ksp4)
and
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070516
SeaMonkey/1.5a] (nightly) (W2Ksp4)

and

[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/2007051513
SeaMonkey/1.5a] (suiterunner, tinderbox-builds) (W2Ksp4)
and
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/2007051610
SeaMonkey/1.5a] (suiterunner, tinderbox-builds) (W2Ksp4)

Both report
[
Failed to load XPCOM component: ...\seamonkey\components\XPCOMUtils.jsm
]
on startup.


[
1.1     sayrer%gmail.com        2007-05-15 16:27                JS code-sharing
module system. Patch by Alex Fritze <[e-mail]> and Robert Sayre
<[e-mail]>. r=shaver/brendan, sr=brendan
]
}}

Comment 1

[Mark Banner (:standard8)]

Caused by bug 238324. This shouldn't affect us at the moment and I would do a patch to add it to the packaging lists but its planned that a move will take place by bug 390870 - so once that is fix, we should revisit this then (adding dep).

Comment 2

[Robert Kaiser]

Actually, I consider this INVALID, as this is no component, and so the error is expected. If it's not, it's a dupe of some toolkit or core thing, but not at all SeaMonkey-specific.

Mark, you probably mean bug 380970 about it maybe moving in path.

Comment 3

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

There's a suggestion in bug 382921 that would eliminate this warning by not reporting errors to load .jsm files.

Comment 4

[Serge Gautherie (:sgautherie)]

For the record,


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/20070529 SeaMonkey/1.5a] (2007-05-29-09-trunk) (W2Ksp4)

The last SMv1.9 nightly still had this bug.


The remaining "tpol-trunk, Gecko/2007053013 SeaMonkey/1.5a" (which is actually based on TK, and not XPFE) still had this bug ... but the file is dated "2007.05.28" so it seems this build had not been clobbered yet.


[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a5pre) Gecko/2007052914 SeaMonkey/2.0a1pre] (2007-05-29-14-trunk) (W2Ksp4)

The first SMv2.0 nightly did not have this bug ... because it didn't have this file at all.

The current "tpol-trunk, Gecko/2007061200 SeaMonkey/2.0a1pre" does not have it either.


Then, it seems this file stopped being packaged when the TK->XPFE switch happened.
I don't know if this is intended, or if we need something like bug 380970 comment 31 (even if that happened 10 days later) ?

Comment 5

[Robert Kaiser]

Sure, with the switch to toolkit, we switched to generating the Windows zip build using the same packaging list as for Windows (NSIS) installer, which means we only copy files that are listed in the packages file - and that file was never listed in there.
We will inlcude it now in the new location that is not causing this problem any more, see bug 351917 comment #24

The warning seen here was fixed by bug 380970 for those builds that have seen it.

Comment 6

[Serge Gautherie (:sgautherie)]

(In reply to comment #5)
> We will inlcude it now in the new location that is not causing this problem any
> more, see bug 351917 comment #24

All is right, then :-)

V.Invalid, as reporter.
(Although I would have preferred Duplicate, but it does not matter much.)