437914 - After upgrading to Firefox 3.0 RC2, extensions can no longer be installed/updated

Status: RESOLVED DUPLICATE of bug 431065

(Toolkit :: Add-ons Manager, defect)

Description

[Bobby Dennett]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080530 Firefox/2.0.0.14 Flock/1.2.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008052906 Firefox/3.0

Had previously installed Firefox 3.0 Beta 5 and installed a handful of extensions without issue.  When RC1 was released, the installation was upgraded and the existing profile worked without issue (including allowing the installation of new extensions and upgrading the ones previously installed).  After upgrading to RC2, extensions can no longer be installed and/or upgraded.  Completely uninstalling Firefox (including removing the existing profile) and reinstalling Firefox 3.0 RC2 fresh has not resolved the issue.

Reproducible: Always

Steps to Reproduce:
1. From the "Add or Remove Programs" control panel, uninstall Firefox 3.0 (selecting the "Remove my Firefox personal data and customizations" option)
2. Delete the "C:\Documents and Settings\<username>\Local Settings\Application Data\Mozilla\Firefox" directory
3. Delete all C:\WINDOWS\Prefetch\FIREFOX* files
4. Delete the "C:\Documents and Settings\<username>\Application Data\Mozilla" directory
5. Install Firefox 3.0 RC2
6. Attempt to install an extension that is supposed to work with RC2 -- for example, NoScript (https://addons.mozilla.org/en-US/firefox/addon/722).
7. The extension gets downloaded but no message is displayed in the Extension Manager/Add-ons window.  Normally, a message is displayed saying that the new extension will be installed after restarting Firefox.
8. Restart Firefox
9. Open the Add-ons window and go to the Extensions "tab".  The extension appears with just the name (no description) and the message, "Not compatible with Firefox 3.0".  Also, the XPI remains in the "<Profile Directory>\extensions\staged-xpis\<Extension-specific Directory>" directory.
Actual Results:  
The extension appears in the Add-ons window / Extension Manager with just the name (no description) and the message, "Not compatible with Firefox 3.0".  Also, the XPI remains in the "<Profile Directory>\extensions\staged-xpis\<Extension-specific Directory>" directory.

Expected Results:  
The extension should have been installed successfully.  Or, if the extension is not compatible with Firefox 3.0 RC2, a message should have been displayed during the extension install process.

Using about:config, I have also tried setting extensions.checkCompatibility to false.  Setting this preference hasn't helped.

Comment 1

[Dave Townsend [:mossop]]

Please set extensions.logging.enabled to true and try installing again and see if anything shows up in the error console.

Comment 2

[Bobby Dennett]

Attempting to re-install the NoScript extension produced the following error 3 times (in the error log; after setting the extensions.logging.enabled parameter to true):

Error: [Exception... "Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIRDFRemoteDataSource.Flush]"  nsresult: "0x80520015 (NS_ERROR_FILE_ACCESS_DENIED)"  location: "JS frame :: file:///C:/Program%20Files/Mozilla.org/Firefox/components/nsExtensionManager.js :: anonymous :: line 8665"  data: no]
Source File: file:///C:/Program%20Files/Mozilla.org/Firefox/components/nsExtensionManager.js
Line: 8665

Comment 3

[Dave Townsend [:mossop]]

Do you have any anti-virus or anti-malware tools installed?

Comment 4

[Dave Townsend [:mossop]]

And do you happen to have TortoiseSVN installed?

Comment 5

[Bobby Dennett]

I do not have TortoiseSVN installed but have several anti-virus/anti-malware tools installed:
  * Symantec AntiVirus 10.1.4.4000 (Corporate Edition)
  * Microsoft Windows Defender
  * PC Tools ThreatFire
  * Lavasoft Ad-Aware 2008
  * Spybot - Search & Destroy (not actively running)

Only Symantec AntiVirus and Windows Defender have been running when I try to install an extension.  I also have Flock 1.2.1 on the affected machine and do not have an issue with the same extensions in that browser.