On Wed, Oct 12, 2011 at 11:24, Florian Hubold <[email protected]> wrote: > Hey there, > > currently nspluginwrapper tries to wrap x86_64 plugins (like native x86_64 > flash player plugin), but there is only i386 npviewer which is needed to run > the plugins.
I'm quite sure we used to have the x86-64 version too > You can see the problem from the following output, which are a > more verbose form of the scripts run through nspluginwrapper filetrigger: > > $ nspluginwrapper -v -i /usr/lib64/mozilla/plugins/libflashplayer.so > *** NSPlugin Viewer *** ERROR: > /usr/lib64/mozilla/plugins/libflashplayer.so: wrong ELF class: ELFCLASS64 > nspluginwrapper: no appropriate viewer found for > /usr/lib64/mozilla/plugins/libflashplayer.so > > In my and Anssi's opinion, nspluginwrapper.script (from nspluginwrapper > filetrigger, > http://svnweb.mageia.org/packages/cauldron/nspluginwrapper/current/SOURCES/nspluginwrapper.script?view=markup > ) should be modified by excluding /usr/lib64. BTW the scripts run during is > nspluginwrapper installation/removal get it right by only using /usr/lib: > http://svnweb.mageia.org/packages/cauldron/nspluginwrapper/current/SPECS/nspluginwrapper.spec?view=markup > Anybody more knowledgeable on nspluginwrapper care to share his opinion, or > are there other reasons for objections? It used to be a good way to separate plugin execution into another process which is good for security/stability but browsers include that feature now > Also are there good reasons to still use nspluginwraper for flash player at > all, as all current browser support out-of-thread execution of plugins and > flash-player-plugin is available as native i586 and x86_64 plugins? Indeed it is now less useful
