Summary: | www-plugins/nspluginwrapper-1.3.0 is not working with any browser | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dmitry <dmitry.ghost99> |
Component: | New packages | Assignee: | Patrick McLean <chutzpah> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | amd64 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
nspluginwrapper build log
emerge --info |
Created attachment 267181 [details]
nspluginwrapper build log
Created attachment 267187 [details]
emerge --info
I have amd64 system.
*** Bug 360415 has been marked as a duplicate of this bug. *** Please don't gzip attachments, it makes them much harder to read. works here. All stable packages... However why did you use -O3 ? Have you tried to compile it or entire system/world with safe cflags?? Don't know why it did not work, but now all installed without "No such file or directory" error, and firefox can detect flash-plugin and NPAPI Plugins Wrapper. I use -O3 flag because of optimizations, and for testing (and for fun). I don't think that -O3 flag can be reason for "ls: cannot access /usr/lib64/nsbrowser/plugins: No such file or directory" error in installing process. Now that bug can be closed. |
After upgrading www-plugins/nspluginwrapper from 1.2.2-r2 to 1.3.0, firefox-3.6, firefox-4 and chromium can't find adobe-flash plugin, and flash isn't work. Downgrading to www-plugins/nspluginwrapper-1.2.2-r2 back flash to work. In emerge log I see: >>> Installing (1 of 1) www-plugins/nspluginwrapper-1.3.0 * Removing wrapper plugins... * Auto installing 32bit plugins... ls: cannot access /usr/lib64/nsbrowser/plugins: No such file or directory * Auto installing 32bit plugins... ls: cannot access /usr/lib64/nsbrowser/plugins: No such file or directory * Any 32bit plugins you currently have installed have now been * configured to work in a 64bit browser. Any plugins you install in * the future will first need to be setup with: * "nspluginwrapper -i <path-to-32bit-plugin>" * before they will function in a 64bit browser It can be the source of problem.