User Agent: Mozilla/5.0 (Windows NT 5.1; rv:6.0.2) Gecko/20100101 Firefox/6.0.2 Build ID: 20110902133214 Steps to reproduce: In tools I choose additional modules then extensions. I see a list of extensions and some of them have been automatically inactivated by Firefox and have a suppress button : I click on this button. Actual results: I see a message saying that the extension will be uninstalled after restart of Firefox. So I close Firefox and restart it : the extension is still in the list... No improvement if I close Firefox then Windows... Expected results: The extension should have disappeared from the list. I have this problem on my machine with : Adobe DLM 1.6.2.99 BarTab 2 CustomizeGoogle 0.76 Dictionnaire français "Classique" 3.5 Dictionnaire français "Reforme 1990" 3.5 Microsoft .NET Framework Assistant 1.2.1

Adobe DLM should uninstall itself automatically after one Firefox run. Microsoft .NET Framework Assistant can't be uninstalled from Firefox. It is installed system wide by Windows updates. But the others should be uninstallable if they are in your profile (in Documents and settings/user/application data/firefox/profile/profilename/extensions). See if they aren't installed in Firefox installation folder (in Program files/firefox/extensions)

1) "Adobe DLM should uninstall itself automatically after one Firefox run." but it remains here after many starts of Firefox ! 2) In the Firefox installation folder I have : - {972ce4c6-7e08-4474-a285-3208198ce6fd}\ from the content of the installed-extensions-processed.txt file : theme,{972ce4c6-7e08-4474-a285-3208198ce6fd} it seems to be a theme. - en-US@dictionaries.addons.mozilla.org\ from the description it is "English United States (en-US) spellchecking dictionary" - staged-xpis\ it is "dictionnaire_myspell_en_fran_ccedil_ais_r_eacute_forme_1990_-1.0.1-fx+zm+tb.xpi" - spell-en-GB.xpi it is "current modern British English" R 1.16, 31/03/03 from is read-me - spell-fr-FR.xpi it is "dictionnaire MySpell pour OpenOffice.org version 1.0.1" from is read-me - Extensions.rdf Its content is " <?xml version="1.0"?> <RDF xmlns:em="http://www.mozilla.org/2004/em-rdf#" xmlns="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> <Seq about="urn:mozilla:extension:root"/> <Seq about="urn:mozilla:theme:root"/> </RDF> " I don't know its use - installed-extensions-processed.txt see first repertory. If there is no way in the extension manager to suppress extensions in the Firefox installation folder this is a bug ! Should this be included in this bug or in an other ? Can I uninstall them the rude way by just erasing the files/directories ? (except theme !)

I think it is a feature of Firefox. The extensions are installed system-wide and will be picked up by any user running Firefox on that system. So no single user should be able to uninstall them system-wide. He can just disable them in his profile using the Addon manager. The administrator can remove those extensions from the Firefox install directory manually. I am not sure it can by done in any way through the Addon manager. Yes, you can just delete those folders and files you don't want there. Leave only the theme. You can read here on the various ways other programs can force extensions on you: https://developer.mozilla.org/en/Adding_Extensions_using_the_Windows_Registry https://developer.mozilla.org/en/Enhanced_Extension_Installation Some of them really can't be removed from inside Firefox, you must remove them via the other programs uninstaller (like the .NET Framework assistant), if it even exists. Can you post a screenshot of addon manager with the stuck extensions (Adobe dlm, google, bartab)?

If they were installed in the system then there wouldn't be an enabled remove button there so that doesn't match up with comment 0. Could you attach a copy of extensions.sqlite and any extensions.log file from the profile folder.

Sorry comments 5 and 6 come from wrong profile

Now you have the 4 requested files.

The seem to be many NS_ERROR_FILE_ACCESS_DENIED errors in the extensions.log file. That could be the reason why Firefox can't remove the extensions. Check your permissions on the E:\MozFF\JC\ folder and subfolders. You need complete read+write access there and also create and delete.

(In reply to :aceman from comment #3) > I think it is a feature of Firefox. The extensions are installed system-wide > and will be picked up by any user running Firefox on that system. I think it is a good feature that avoid to duplicate installation in all the profiles of all the users for extensions that are needed by all of them e.g. dictionaries for local language(s) and English/US and others widely used extensions. In my particular case I have created limited right Windows users for my children when they are at home and for me a limited right that I use for surfing (for security reason) and the administrator that means 12 to 15 profiles... The users need a way to manage (install, disable or uninstall) the system-wide extensions. Brute force uninstall by erasing the files may be a work around if this does not cause problems (e.g. in the registry) but I prefer an UI ! It seems that the present extension manager works only on a profile ; Why not creating a third category that works on ALL the profiles of a particular user : there should be no problem of rights of access to the files as in system-wide.

(In reply to Jean-Marie COUPRIE from comment #13) > (In reply to :aceman from comment #3) > > I think it is a feature of Firefox. The extensions are installed system-wide > > and will be picked up by any user running Firefox on that system. > I think it is a good feature that avoid to duplicate installation in all the > profiles of all the users for extensions that are needed by all of them e.g. > dictionaries for local language(s) and English/US and others widely used > extensions. > In my particular case I have created limited right Windows users for my > children when they are at home and for me a limited right that I use for > surfing (for security reason) and the administrator that means 12 to 15 > profiles... > The users need a way to manage (install, disable or uninstall) the > system-wide extensions. Brute force uninstall by erasing the files may be a > work around if this does not cause problems (e.g. in the registry) but I > prefer an UI ! > It seems that the present extension manager works only on a profile ; Why > not creating a third category that works on ALL the profiles of a particular > user : there should be no problem of rights of access to the files as in > system-wide. There is a third category of add-ons that work for all the profiles of a particular user, the user's registry for example. See https://developer.mozilla.org/en/Installing_extensions and https://developer.mozilla.org/en/Adding_Extensions_using_the_Windows_Registry If I uninstall you correctly you're saying that Firefox cannot write to the location that those extensions are installed to, that matches what the logs seem to say and that is why we can't uninstall them. Disabling them gets you basically the same result but we should be providing a way to make Firefox ignore them altogether. Bug 640775 is for doing that so I'm going to duplicate this there. Please re-open if I've misread the situation

(In reply to :aceman from comment #12) > The seem to be many NS_ERROR_FILE_ACCESS_DENIED errors in the extensions.log > file. That could be the reason why Firefox can't remove the extensions. > > Check your permissions on the E:\MozFF\JC\ folder and subfolders. You need > complete read+write access there and also create and delete. You are right. Instead of checking my permissions on the E:\MozFF\JC\ folder and subfolders (that would have been very long and tedious) I have made a copy of them on a FAT32 partition as a "test" profile and linked this to my other profiles. The trick is that copy from NTFS to FAT32 does not transfer the NTFS permissions and reset to default values : the owner has all the rights... After this I tried to uninstall the extensions : SUCCESS !

(In reply to Dave Townsend (:Mossop) from comment #14) > (In reply to Jean-Marie COUPRIE from comment #13) > ... Please re-open if I've misread the situation > > *** This bug has been marked as a duplicate of bug 640775 *** Please give advice : 1) As you can see from Comment 15 correct permissions solve the problem of uninstalling but I have found other problems : there are many errors in extension.log (that normal user ignore) but I have seen NONE of them on my screen when they occurred. I think that this is a bug. Do I have to fill a separate bug report for this ? Or do we process this here by reopening the bug ? 2) I think that the users need a way to manage (install, disable or uninstall) the user wide (with limited user rights) and system-wide (with administrator rights) extensions. This is more than offered by bug 640775. Do I have to fill a separate bug report for this ? Or do we process this inside the bug 640775 ? I think that (because it use edit of the registry) https://developer.mozilla.org/en/Adding_Extensions_using_the_Windows_Registry should be reserved to Geeks or developers and https://developer.mozilla.org/en/Installing_extensions to experienced or expert users (I'll try it) and an UI (probably an improvement of extensions manager) is needed for the newbies.

(In reply to Jean-Marie COUPRIE from comment #16) > (In reply to Dave Townsend (:Mossop) from comment #14) > > (In reply to Jean-Marie COUPRIE from comment #13) > > ... Please re-open if I've misread the situation > > > > *** This bug has been marked as a duplicate of bug 640775 *** > > Please give advice : > 1) As you can see from Comment 15 correct permissions solve the problem of > uninstalling but I have found other problems : there are many errors in > extension.log (that normal user ignore) but I have seen NONE of them on my > screen when they occurred. I think that this is a bug. Do I have to fill a > separate bug report for this ? Or do we process this here by reopening the > bug ? [...] It's not a bug, it's a feature. The idea is to proceed "as best we can" even against faulty input, without interrupting the user's thought with popups all over the place. The error messages were logged (so debugging can be done later) and they may also, in addition, have been sent to stderr (which, for a GUI, is usually, but not necessarily, /dev/null) and/or to the Error Console.

(In reply to Tony Mechelynck [:tonymec] from comment #17) > [...] > > It's not a bug, it's a feature. The idea is to proceed "as best we can" even > against faulty input, without interrupting the user's thought with popups > all over the place. > > The error messages were logged (so debugging can be done later) and they may > also, in addition, have been sent to stderr (which, for a GUI, is usually, > but not necessarily, /dev/null) and/or to the Error Console. This is probably an example of wrong implementation of a good idea "not bothering the users with many error messages" ! If I have mistyped a command, say it immediately (instead of just log it in a log the existence of which most users do not know) else I'll conclude that the Mozilla program does not work and choose one of its competitor. If the program can recover from the error it is nice to just log it without error message...