In short, nspluginwrapper-1.4.0-r1 doesn't make/keep the /usr/{lib32,64}/nsbrowser/plugins dir. Because of this, when a plugin tries to do a nspluginwrapper -i as root (as the ebuilds such as adobe-flash would do), the plugin is installed to /root/.mozilla/plugins/ in stead of /usr/lib64/nsbrowser/plugins. This is, needless to say, an issue because plugins such as adobe-flash (especially the newest amd64 version which only has a 32 bit version) will only run in browsers started as root. Reproducible: Always Steps to Reproduce: 1. Install nspluginwrapper-1.4.0-r1 and adobe-flash-10.3.181.14-r1 (without any other plugins installed) 2. Wonder why flash isn't working. :P Actual Results: adobe-flash (and other plugins) do not work in browsers run as a normal user. Expected Results: adobe-flash (and other plugins) should work in browsers run as a normal user.
I wonder how issue like it happen, *someone* did not tested the changes before he commit it to gentoo's cvs I presume. As a quick workaround, 'umask 022 && mkdir -p /usr/lib64/nsbrowser/plugins' do the trick.
Looks like in the past 3-5 days a placeholder file was removed, which would mean that the dir no longer exists. I assume that a keepdir /usr/lib/nsbroswer/plugins would work because the plugins are always installed to /usr/lib32/nsbrowser/plugins if they're 32 bit and lib (on 64 bit systems) is a symlink to lib32. The problem only shows up when there's only 32-bit plugins installed and you're on a 64 bit system, unless I'm mistaken.
This is fixed in CVS. Re #1: All ebuilds are tested before being committed, but generally not on a clean stage3. Gentoo developers are volunteers that do not have time to build an entire system for every commit. Test machines generally have other packages installed, such as packages that include 64 bit plugins.
(In reply to comment #3) > This is fixed in CVS. > > Re #1: All ebuilds are tested before being committed, but generally not on a > clean stage3. Gentoo developers are volunteers that do not have time to build > an entire system for every commit. Test machines generally have other packages > installed, such as packages that include 64 bit plugins. That is not true. From time to time I hit a ebuild bump what does not even build. I follow bugzilla, CC myself on such bugs etc. Anyway, thanks for fixing the flash.
Should this be bumped to -r2? Since anyone who was on -r1 may be broken if they only had the flash plugin installed. A bump should fix it, I think.
