226181 - -239 chrome error (nsresult code: 0x80004005)

Status: RESOLVED INVALID

(Core Graveyard :: Installer: XPInstall Engine, defect)

Description

[Henrik Gemal]

Just go the dreaded -239 install error. this time it has the debug info in it:

     ** ForceContentType version 0.3 being installed on 2003111608
     ** Installation method is 2
     ** ok adding jar file.
     ** ok adding service.
     ** ok registering the content chrome.
     ** ok registering the locale chrome.
     [1/5]	Installing: C:\Private\Mail\MozillaFirebird\PowerP\chrome\forcect.jar
     [2/5]	Installing:
C:\Private\Mail\MozillaFirebird\PowerP\chrome\forcectService.js
     [3/5]	Installing:
C:\Private\Mail\MozillaFirebird\PowerP\chrome\forcectService.xpt
     [4/5]	Register Package:
jar:file:///C:/Private/Mail/MozillaFirebird/PowerP/chrome/forcect.jar!/content/forcect/
     ** InstallSkin() failed. - nsresult code: 0x80004005
     ** InstallLocale() failed. - nsresult code: 0x80004005
     ** InstallPackage() failed. - nsresult code: 0x80004005
     ** Failed to register chrome. - nsresult code: 0x80004005
     ** Problem performing install. Error code: -239
     ** Problem installing. Error code: -239. Error codes can been seen at:
http://devedge.netscape.com/library/manuals/2001/xpinstall/1.0/err.html

Then I tried to install it again and it worked!

Comment 1

[Henrik Gemal]

Attachment: install.log file with -239 error and success

Comment 2

[HJ]

Henrik, is that 100% reproducable? If so, add your chrome.rdf (before and after
the installation) as attachments. That should tell us a little bit more about
the exact cause of the error.

Comment 3

[HJ]

I wonder about the two different installation methods: ** Installation method is
1/2 in install.log Why is that? Can you attach the corresponding install.js? 

1 = C:\Private\Mail\MozillaFirebird\PowerP\chrome\XXXXXX
2 = C:\Program Files\Mozilla.org\nightly\MozillaFirebird\chrome\XXXXXX

So 1 failed and 2 was successfull, now that is interesting...

Comment 4

[Henrik Gemal]

sorry about the two different inst methods.

with a clean install and clean profile I can reproduce every time.'

the chrome.rdf in both the profile and program dir doesn't contain any info
about forcecontenttype

install.js is:
http://www.mozdev.org/source/browse/~checkout~/forcecontenttype/src/install.js

Comment 5

[DocWilco]

Do you get the same behaviour (1st time fails, 2nd time succeeds) when you use
the same install method both times?

Comment 6

[Robert Kaiser]

This summary is very little descriptive and could attract people who have
completely different problems that lead to a -239, so adding the nsresult code
from Comment #0

Comment 7

[DocWilco]

I think I have found the problem. Not as much a problem with Mozilla as it is
with the install.js/jarfile. Though I must say Mozilla could be a bit more
verbose about it. I guess I'll look into that.

The problem is one of paths within the jarfile. In install.js this code is featured:

err_tmp = registerChrome(PACKAGE | PROFILE_CHROME, sysChromeUserJar, "content/"
+ myProductRegKey + "/");

Which makes Mozilla look for content/forcect/contents.rdf, but the forcect.jar
contains:

Archive:  forcect.jar
  Length     Date   Time    Name
 --------    ----   ----    ----
     1094  06-13-03 18:14   content/contents.rdf
     2401  06-13-03 18:14   content/forcectOverlay.xul
     2139  05-27-03 20:57   content/forcectOverlay.js
     8134  06-13-03 18:14   content/forcectFiltersDialog.js
     4164  06-13-03 18:14   content/forcectFiltersDialog.xul
      725  05-27-03 20:57   locale/en-US/forcect/contents.rdf
      837  05-27-03 20:57   locale/en-US/forcect/forcect.dtd
 --------                   -------
    19494                   7 files

As you can see, the forcect subdir is missing from the content dir.

When I rebuild the jarfile and the XPI with the proper structure, I do not get a
-239. The reason the -239 does not occur when installing in the global chrome
dir is because CHROME_DELAYED is used in that case. But it is not succesful as
far as I can tell. (I did not see the extra menu item until I succesfully
installed my own XPI-file in my profile, did not test it with global dir.)

IMHO this bug can be closed.

Comment 8

[DocWilco]

I reproduced at home and also reproduced my fixing of the XPI.

http://bsdchicks.com/forcect-0.3-drwilco.xpi