Closed
Bug 669590
Opened 13 years ago
Closed 13 years ago
What happened:TypeError:Components.classes['@mozilla.org/extensions/manager;1'] is undefined
Categories
(Firefox :: General, defect, P5)
Tracking
()
RESOLVED
DUPLICATE
of bug 578099
People
(Reporter: anandarony, Unassigned)
Details
Attachments
(1 file)
13.93 KB,
image/jpeg
|
Details |
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0 Build ID: 20110615151330 Actual results: 1. Click on Mozilla Firefox icon 2. An Error message displayed is pop-up "What happened:TypeError:Components.classes['@mozilla.org/extensions/manager;1'] is undefined" 3. Click on ok button 4. Mozilla Firefox browser opened
Reporter | ||
Comment 1•13 years ago
|
||
I was using 4.1 but when gotten the above error message then update Firfox version 4.1 to 5.0 But problem not solved
Reporter | ||
Updated•13 years ago
|
Priority: -- → P5
Comment 2•13 years ago
|
||
Not a security issue. This is very likely an extension which was written for Firefox 3.6 and never updated for Firefox 4. Does this happen if you launch in safe mode?
Group: core-security
Comment 3•13 years ago
|
||
The culprit is most likely the Ask.com toolbar.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Comment 4•13 years ago
|
||
Please, please contact me about this. I work on the Ask.com toolbar, and I want to resolve any issues we're causing in the field.
Comment 5•13 years ago
|
||
(In reply to Alex Vincent [:WeirdAl] from comment #4) > Please, please contact me about this. I work on the Ask.com toolbar, and I > want to resolve any issues we're causing in the field. It's the same issue that was reported quite some time ago and reportedly fixed in newer Ask.com toolbar versions. It continued to affect Firefox 5 after 4 because it used a bogus max supported version entry saying it supported up to Firefox 5.* when 4 wasn't even yet released at the time and it supported neither. Installing a current toolbar version should fix it if the user wishes to still use it, though I don't know what the update route is if it's not using the normal automatic updating. Updating Firefox to 6.0 will avoid it now as we're finally past the bogus stated support range.
You need to log in
before you can comment on or make changes to this bug.
Description
•