Issues related to pluginsFrom MozillaZine Knowledge BaseThis article explains how to identify and disable installed plugins in Firefox and Mozilla Suite/SeaMonkey. If you suspect that a problem with your Mozilla browser issue is related to a plugin, you should perform the standard diagnostic steps first, to rule out problems caused by other issues such as problematic extensions or profile issues. If you already know that your issue is related to a specific plugin because of problems with certain web content or because you received an error message identifying the plugin, look through the articles in the Category:Plugins for a solution.
[edit] BackgroundMozilla browsers often need plugins for web content that cannot be handled internally, such as Java applets, Flash movies and embedded audio and video. (Note that JavaScript is often required for Flash to run correctly. Note also that JavaScript is neither a plugin nor Java.) Mozilla browsers find installed plugins by searching in different locations [1]. On Windows, common plugins are located via plugin scanning; other plugins are detected in the Mozilla browser installation directory "plugins" folder (e.g., in Firefox, C:\Program Files\Mozilla Firefox\plugins). If different plugins for the same MIME type are found in multiple locations, the plugin found in the installation directory plugins folder will normally be used.  Starting in Firefox 3, and in SeaMonkey 2 (not yet released), you can view, disable, and enable plugins from the "Tools" menu, via "Add-ons (Add-on Manager) -> Plugins". To disable a specific plugin in Firefox 3 or SeaMonkey 2, you can open the Add-ons window, select the plugin you wish to disable, and click the Disable button, as shown in this SeaMonkey 2 screenshot. You should use this new feature instead of disabling plugins by manually renaming or removing the associated plugin files as described below. [2] Also starting in Firefox 3, plugin versions that are known to cause crashes or other problems are added to the Add-ons Blocklist and are automatically disabled. [3] For example, the older Quicktime plugin version 7.1.x for Windows has been blocklisted and is disabled automatically in Firefox 3. [4] Since older versions of plugins may have bugs that are fixed in newer versions, you should keep your plugins updated, as a general rule. You can diagnose problems you suspect are plugin-related by removing or disabling the plugin. If the problem goes away, it was caused by the plugin. Keep in mind that if you disable or remove a plugin, embedded web content handled by that plugin will be missing and you may receive a "missing plugin" alert. [edit] Identifying installed pluginsYou can see a list of detected plugins by entering about:plugins in the Location Bar (address bar). The installed plugins list will include the file name and a description of the plugin along with the associated MIME types handled by each plugin. On Windows, all Mozilla browser plugin file names begin with np and end with .dll. (Note that some plugins like Quicktime or Java include multiple plugin files, each with a different file name.) If you set the plugin.expose_full_path preference to true in about:config, you will be able to see the full path to each plugin file in the about:plugins list, instead of just the file name. [edit] Mozilla Default Plug-inOn Windows, Mozilla browser installations include the Mozilla Default Plug-in "npnul32.dll", located in the browser installation directory "plugins" folder. Mozilla Suite and SeaMonkey need this plugin for the "click here to get the plugin" alert on web pages that need plugins that are missing. Firefox does not require this plugin as the "Additional plugins are required..." yellow message bar will display without it. [edit] Disabling plugins found in the plugins folderApplies to Windows systems You can temporarily disable some of the plugins that your Mozilla browser is detecting by renaming or removing the associated files from the installation directory "plugins" folder, as follows: [edit] Firefox
If the problem persists, you should check the about:plugins list again to see what plugins are still being detected via plugin scanning. Additionally, some programs that include browser plugins such as Quicktime may copy back any removed plugin files to the browser plugins folder. If the problem goes away, it was caused by one of the disabled plugins. You can try to identify the problematic plugin and restore the other plugin files or you can simply reinstall any missing plugins as needed. [edit] Mozilla Suite or SeaMonkeyFollow the same procedure given above, except do not rename or remove the Mozilla Default Plug-in "npnul32.dll" from the Mozilla Suite or SeaMonkey installation directory "plugins" folder, since this file is needed for missing plugin alerts (see above). [edit] Disabling the automatic plugin scanApplies to Windows systems On Windows systems, Mozilla browsers will scan for common plugins in other locations, even if the browser plugins folder is empty. You can prevent the automatic scan for for common plugins such as Windows Media Player or Real Player by modifying the related preference settings. For detailed instructions, see this article. Note that some plugins that are detected via plugin scanning such as Java or Adobe Reader can be disabled by other methods, described below. [edit] Other methods of disabling plugins
[edit] Problematic pluginsApplies to Windows systems Your Mozilla application, a Mozilla extension or the application that includes the plugin may provide a user interface where you can disable a plugin. See the other methods of disabling plugins given above. If there is no user interface to disable the plugin, you must manually disable it, either by moving the plugin file to another location or by renaming it (to rename a plugin, add an "X" in front of the file name). The following plugins have been known to cause problems in Mozilla applications (this is not a complete list). Plugins listed below are located in the browser plugins folder (e.g., for Firefox, in C:\Program Files\Mozilla Firefox\plugins) unless another location is given. Note: Plugin locations can be found by setting plugin.expose_full_path to true in about:config and then checking the file path in about:plugins.
[edit] Download manager pluginsDownload manager plugins are known to cause problems downloading or saving files, if the application is later uninstalled or otherwise stops working, if the associated plugins are still in place. Such plugins include:
Information about other Download Managers can be found at PluginDoc. [edit] Outdated plugins placed in the browser plugins folderOutdated versions of plugins that have been copied to the browser plugins folder may conflict with the currently installed version.
[edit] See also
[edit] External links[edit] Related bug reports |
|