Red Hat Bugzilla – Bug 120469
Installs of extensions fail as normal user
Last modified: 2007-11-30 17:10:40 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312 Description of problem: Attempts at installing certain extensions succeed if running mozilla as root, but fail otherwise. For example, attempts at installing "home button", "banner blind", or "jre" seem to work as root, but fail with various error messages. (home button fails with "chrome registration failed"). Here is a snippet from the install.log: ------------------------------------------------------------------------------- file:///home/tbl/Download/mozExtensions/home.xpi -- 04/08/2004 18:44:28 ------------------------------------------------------------------------------- Home Button (version 0.6) ----------- [1/4] Installing: /home/tbl/.mozilla/Pass1/etitruej.slt/chrome/home.jar [2/4] Register Content: jar:file:///home/tbl/.mozilla/Pass1/etitruej.slt/chrome/home.jar!/content/ ** opening of installed-chrome.txt failed. - nsresult code: 0x80520015 ** /usr/lib/mozilla-1.6/chrome/installed-chrome.txt ** opening of installed-chrome.txt failed. - nsresult code: 0x80520015 ** Failed to register chrome. - nsresult code: 0x80520015 Install **FAILED** with error -239 -- 04/08/2004 18:44:32 Version-Release number of selected component (if applicable): mozilla-1.6-2 How reproducible: Always Steps to Reproduce: 1. download home.xpi from mozdev.org 2. start mozilla as non-root 3. File->Open File... home.xpi Actual Results: installation fails as normal user, but succeeds as root. Expected Results: successful installation Additional info: (Installion of some other extensions succeed: adblocker, ...)
I can't fix this since this is a problem with the package. It assumes that it can be installed into the system directory.
hmmm... it asks whether to install in profile for system directory. I replied profile. I'm guessing it is still trying to open something in the system directory (/usr/lib/mozilla-1.6/....) This is going to be a interesting challenge getting extension developers to behave ......