NPAPI 11.x plugin with flash-player-plugin package. Also dealing with $HOME/.mozilla/firefox/.default/pluginreg.dat might be used as workaround in case of problems about plugin (re)detection. Alternatively it can be cleaned $HOME/.mozilla (losing the configuration) or create a new firefox profile. Touch /opt//opt/google/chrome/PepperFlash/libpepflashplayer.soīut in this way would alter the RPM's MD5 (in the timestamp) of the package. Touch /usr//mozilla/plugins/libfreshwrapper-flashplayer.so A trick (that however not always works 100%) is to upgrade the timestamp of both (by just running: The best dir to place the pepper library is /opt/google/chrome/PepperFlash/libpepflashplayer.so, in that way is also recognized by chromium and chrome without any further addition.Ī minor glitch exists, and is that if you upgrade freshplayerplugin package without upgrading the ppapi plugin or viceversa just upgrade the ppapi plugin package without the freshplayerplygin, firefox could have difficult in recognizing the change and still thinks to deal with the old version. when firefox is ran trough ssh for instance, haven't tried under NX).
PPAPI 23.x plugin bundled with freshplayerplugin package wrapper: works locally on a firefox with also freshplayerplugin 0.3.x package installed.
0 kommentar(er)
