Firefox--Multiple plugins Directories

There are a number of legitimate reasons why one would have multiple versions of Firefox installed on one system.  While, it's generally ill-advised to have multiple versions of the same package/software installed--as it could create resource conflicts and system hangups--recent versions of Firefox have become more stable in this type of scenario.  The Developer Edition of Firefox, for example, has an option under Preferences that specifies whether or not to "allow Firefox Developer Edition and Firefox to run at the same time" through the use of different Profiles.

While this is a nice functionality, there are still some issues with the system-wide Library path and the local ".mozilla" directory in the user's home directory.  There's still an issue with installed plugins, which are in the system-wide directory "/usr/lib64/mozilla/plugins/" on a 64-bit system, not available in the second installed firefox package unless the user creates links to them in the "~/.mozilla/plugins/" directory.  However, the primary installation of firefox, which is presumably installed through the package manager on a Linux system, also uses the user's local "~/.mozilla/" directory.

As an alternative option to linking the system-wide plugins to the local ".mozilla" directory, one can also refer to a custom MOZ_PLUGIN_PATH that the Firefox Developer Edition consults as it's launched from a script. 

#!/bin/env bash
export MOZ_PLUGIN_PATH="/home/ilmostro/firefox/myplugins"
exec /home/ilmostro/firefox/firefox -P dev-edition-default
exit

That's an example in a bash shell, where the custom plugins directory is declared, the second "developer edition" of firefox is launched (presumably housed in the user's home/firefox directory) with the "developer-edition" profile selected.

Popular posts from this blog

Password Policy in RHEL 7

Centos 7 pulseaudio

wpa_supplicant and wifi in RHEL 7