As of firefox-bin-21.0 the plugins link must be created under /opt/firefox/browser. But nsplugins creates it in /opt/firefox. Thus adobe-flash is no longer working with firefox. Reproducible: Always Steps to Reproduce: emerge firefox-bin adobe-flash browse vimeo.com
adding Jeff as he submitted the firefox-bin ebuild
I can confirm this bug. Simple workaround: cd /opt/firefox/browser sudo ln -s ../plugins .
(In reply to comment #2) > I can confirm this bug. > Simple workaround: > cd /opt/firefox/browser > sudo ln -s ../plugins . This is not a bug but a deliberate change (see http://www.ghacks.net/2013/05/15/why-you-may-have-lost-access-to-plugins-or-extensions-in-firefox-21/) Moving the plugins link into the browser directory is the correct course of action.
I just worked around it at the eclass level like this: --- nsplugins.eclass 2012-09-15 11:31:15.000000000 -0500 +++ nsplugins.eclass.1 2013-05-16 18:40:41.052430365 -0500 @@ -73,4 +73,5 @@ fi dosym "${PLUGIN_BASE_PATH}/nsbrowser/plugins" "${MOZILLA_FIVE_HOME}/plugins" + dosym "${PLUGIN_BASE_PATH}/nsbrowser/plugins" "${MOZILLA_FIVE_HOME}/browser/plugins" }
*** Bug 470162 has been marked as a duplicate of this bug. ***
*** Bug 471254 has been marked as a duplicate of this bug. ***
This does not seem to be fixed. I installed firefox-bin-21.0 on Thu May 16 18:57:39 2013, and there was no revision bump since then, and I still see the broken behaviour.
(In reply to Dennis Schridde from comment #7) > This does not seem to be fixed. I installed firefox-bin-21.0 on Thu May 16 > 18:57:39 2013, and there was no revision bump since then, and I still see > the broken behaviour. There is no revision bump on eclass changes, you can sync up and re-emerge for a proper plugin setup.
*** Bug 472798 has been marked as a duplicate of this bug. ***
