Closed Bug 318760 Opened 20 years ago Closed 19 years ago

Extension Manager falsely indicates extensions will be enabled/deleted on restart

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED DUPLICATE of bug 323826

People

(Reporter: dan0, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 I've upgraded from v1.0.5 to v1.5 and when upgrading my installed, or adding new, extensions (and themes, for that matter) the dialog next to the extension claims: "Extension" will be upgraded/installed/uninstalled when Firefox is restarted. This does not happen. The list of Extensions affected is: DOM Inspector 1.8 (install) Forecastfox 0.8.2.4 (upgrade) Translation Panel 1.4.13 (uninstall) Translation Panel 1.4.13+ (install) Habari Xenu 1.0.1 (upgrade) Sage 1.3.6 (install) Wizz RSS Newsreader 2.0.1 (install) FWIW, JavaScript Debugger 0.9.84 is disabled/not compatible Reproducible: Always Steps to Reproduce: 1.attempt to remove/add/upgrade Extension 2.Restart Firefox 3. repeat Actual Results: I get the abaove emntioned messages in the Extensions Alert box and if the Extensions was working before the upgrade, like Forecastfox, it no longer works after restarting Firefox. Expected Results: Installed/removed/upgraded extensions
Dan, can you zip up your profile's extensions directory along with the extensions.rdf, extensions.cache, and extensions.ini files that are located inside your profile's directory and then attach it to this bug or email them to me? http://www.mozilla.org/support/firefox/profile
Dan, are you still experiencing this? If so, can you attach the files as asked for in comment #2?
This was fixed by the patch for bug 323826 *** This bug has been marked as a duplicate of 323826 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.