63504 - x.themes.org themes don't autoinstall

Status: VERIFIED INVALID

(SeaMonkey :: Installer, defect)

Description

[adam shostack]

(Not sure if this is an XPI installer issue or some other component.)

When attempting to quick load themes off of x.themes.org, I get an "Unknown
error" as the installer attempts to install the theme.



Document http://x.themes.org/viewresources.phtml?type=chrome loaded successfully

we don't handle eBorderStyle_close yet... please fix me
Adding element 0 : _blank
we don't handle eBorderStyle_close yet... please fix me
2
Adding Progress element 0 : _blank
we don't handle eBorderStyle_close yet... please fix meError loading URL
http://x.themes.org/php/download.phtml?query=download&object=resources.chrome.971820033&server=themes.org:
804b0002

Comment 1

[R.K.Aa.]

possible dup of bug 59776

Reporter: Please include mozilla build ID

Comment 2

[adam shostack]

Build ID: 2000121908

Comment 3

[Sean Su]

cc'ing dveditz

Comment 4

[Daniel Veditz [:dveditz]]

Could you attach a copy of the relevant section of your install.log please? 
It'll either be in the bin directory if you have write permission there, or in 
your profile directory if you don't.

I don't know the format used by x.themes.org, but they might be attempting to 
install the themes "globally", which is likely to fail if the directory is 
write protected. They could write their scripts to get around this, but 
probably didn't.

Comment 5

[adam shostack]

Yes, it was a permissions problem on a global install.  Changing permissions on
those files allowed me to install the new themes.  Could I suggest that in the
short term the installer error include a pointer to the install.log file? 
(Longer term, I think mentioning a lack of permission would be good.)



http://x.themes.org/downloads/chrome.971820033.xpi  --  12/22/2000 10:53:08
-------------------------------------------------------------------------------

     GrayModern 0.41
     ---------------

     ** initInstall: 0
     ** chrome_dir = /usr/local/mozilla/package/chrome/
     ** ERROR (-225): Installing: /usr/local/mozilla/package/chrome/gray_modern0
3.jar
     ** addFile: -225
     ** jar = /usr/local/mozilla/package/chrome/gray_modern03.jar/
     ** ERROR (-214): Register Skin: 
     ** ERROR (-214): Register Skin: 
     ** ERROR (-214): Register Skin: 
     ** ERROR (-214): Register Skin: 
     ** ERROR (-214): Register Skin: 
     ** ERROR (-214): Register Skin: 

     Install **FAILED** with error -225
     ** cancelInstall: undefined
     Finished Installation  12/22/2000 10:53:10

Comment 6

[Daniel Veditz [:dveditz]]

So how do you report themes against x.themes.org? Probably not going to be seen 
here.

The install engine generates the install log to help debug cases like this, but 
leaves all the UI up to the triggering site (which can get a status callback if 
they wish) and the install script (which can pop up alert messages).

We do have a plan to split the -225 "extraction error" into finer grained 
errors; that's covered in another bug. (write permission problem, file not 
found in the archive, out of disk space, archive corrupt).

Marking INVALID because this is really an x.themes.org problem as far as i can 
see.

Comment 7

[Grace Bush]

vfy