Closed
Bug 310322
Opened 19 years ago
Closed 19 years ago
Firefox won't start after installation of this extension
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: vassoura, Unassigned)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: Mozilla Firefox 1.0.6 Brazilian Portuguese - URL:https://addons.mozilla.org/extensions/moreinfo.php?application=firefox&category=Image%20Browsing&numpg=10&id=843 After installing the autoembedder Firefox didn't work anymore. I reinstalled it 3 times (both the Firefox 1.0.6 Brazilian Portuguese and the Firefox 1.0.7 Portuguese), I erased all the folders after each installation and it still didn't work. When I click on Firefox's icon it won't even start. I think I have to clean the registry before I can use it again, could you tell me what to look for and to change? Reproducible: Couldn't Reproduce Steps to Reproduce: This is what I did when it worked: 1.Run Firefox 2.Search for the autoembedder extension 3.Install it 4.Firefox crashes and it never works again Actual Results: Firefox stopped working Expected Results: Allow me to view JPEGs automatically, without havig to choose a supported file by firefox Theme-{972ce4c6-7e08-4474-a285-3208198ce6fd} Extensions-Noscript Getflash
You may need to use a new profile: http://www.mozilla.org/support/firefox/profile. Also try safe mode: http://www.mozilla.org/support/firefox/faq#troubleshooting
Updated•19 years ago
|
Version: unspecified → 1.0 Branch
Comment 2•19 years ago
|
||
Reporter - have you tried the items as suggested in comment #1 and if so what were the results?
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Updated•19 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•19 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•