Error: e.location.getItemLocation(e.id) is undefined Source File: file:///C:/Program%20Files%20(x86)/Mozilla%20Firefox/components/nsExtensionManager.js Line: 4082

RESOLVED INCOMPLETE

Status

()

Toolkit
Add-ons Manager
RESOLVED INCOMPLETE
9 years ago
9 years ago

People

(Reporter: mozills, Unassigned)

Tracking

1.9.0 Branch
x86
Windows Vista
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.10) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)

after the most recent update (3.0.10)- all Extentions fail to run, and any attempts to download new extentions fail with the Error: e.location.getItemLocation(e.id) is undefined
Source File: file:///C:/Program%20Files%20(x86)/Mozilla%20Firefox/components/nsExtensionManager.js
Line: 4082

I had uninstalled- then reinstalled Firefox again to confirm the problem.




Reproducible: Always

Steps to Reproduce:
1. tools -> addons -> get addon (any)
2. wait for install button to appear, click it - then wait.
3. failure confirms.

Actual Results:  
Firefox could not install the file at 

https://addons.mozilla.org/downloads/file/49054/ad_blocker-0.6.4-fx.xpi

because: Unexpected installation error
Review the Error Console log for more details.
-203

the error console log states the previously mentioned error.

Expected Results:  
installed the extension.
(Reporter)

Updated

9 years ago
Version: unspecified → 3.0 Branch
could be related to bug 443885
Component: Extension Compatibility → Add-ons Manager
Product: Firefox → Toolkit
QA Contact: extension.compatibility → add-ons.manager
Version: 3.0 Branch → 1.9.0 Branch
Please attach copies of extensions.rdf, extensions.cache, extensions.ini and extensions.log from your profile folder to this bug report.

http://support.mozilla.com/en-US/kb/Profiles
Unable to evaluate this bug further without the information requested in comment 2. Please reopen if you can provide that.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.