To view parent comment, click here.
To read all comments associated with this story, please click here.
Maybe this are two solutions:
"The reason for this is that NSPluginWrapper 'wraps' 32bit plugins in such a way that other 64bit browsers can use 32bit plugins. It does this by creating a 64bit executable named 'npwrapper.originalpluginname' for each 32bit plugin and this in term runs the real 32bit executable. This works very nicely for Firefox, which cannot handle plugins of a different architecture itself.
Opera however, doesn't need NSPluginWrapper and indeed all it does is serve to cause our own wrapper (which performs the same purpose) to get confused, since we detect the architecture of the NSPluginWrapper (64bit) instead of the actual plugin (32bit). What we need to do is ignore all NSPluginWrapper wrapped plugins by default and indeed there is a bug filed suggesting we do exactly that. In the mean time we do have a system for setting certain plugins to be ignored."




Member since:
2006-11-13
Yes, including yours. :-)
On my Ubuntu 10.04 (64-bit) system, if I copy the 32bit flash plugin (*.so file) into Firefox's plugin folder, it doesn't show up at all in the about:plugins page - flash is completely disabled.
So back to the older v10.0 64-bit flash plugin.