> in Firefox when I use browser-plugin-freshplayer-pepperflash
> with adobe-flashplugin I see two different versions of the
> Flash plugin and I am not able to force the use of the PPAPI
> version
>
> OK after some more trying it appears that Firefox cannot tell
> the NPAPI and PPAPI plugins apart when both are installed
This is because both look like NPAPI plugins to Firefox (which incidentally does not support PPAPI plugins anyway): the PPAPI plugin installed by adobe-flashplugin is wrapped as a NPAPI plugin by browser-plugin-freshplayer-pepperflash. But you (and Firefox) can still tell the difference from the version numbers.
As mentioned in my previous comment, I suggest using Andrei Alin's version of browser-plugin-freshplayer-pepperflash instead of the one in the Ubuntu repository. It will set up the symlinks so that only the wrapped PPAPI plugin is shown to Firefox, not the NPAPI plugin.
> some websites will start the NPAPI plugin and some other will
> run the PPAPI plugin
Are you sure about that? I've always thought only the higher-version plugin was used by Firefox, so, the wrapped PPAPI plugin. I've never seen Firefox start the lower-version plugin when running Flash content on the web, but I'm not checking every time though.
> Disabling one of the plugins does not work either because the
> setting is applied to both plugins (this is visible after
> reloading the plugin setting menu).
Yes, this is irritating. Again, Andrei Alin's version.
> This makes browser-plugin-freshplayer-pepperflash mostly useless
> and "solves" my both issues, I will just stick to adobe-flashplugin
> and remove browser-plugin-freshplayer-pepperflash and
> pepperflashplugin-nonfree
I don't see how this solves anything, and if you do that, your Firefox will use the deprecated 11.2 NPAPI Flash plugin, because you'll have removed the PPAPI/NPAPI wrapper (browser-plugin-freshplayer-pepperflash).
Now the 11.2 NPAPI plugin is still supported security-wise, so that may be enough for your needs, while waiting for the updated new NPAPI plugin to exit beta.
Last remarks about the wrapper: Stéphane:
> in Firefox when I use browser- plugin- freshplayer- pepperflash
> with adobe-flashplugin I see two different versions of the
> Flash plugin and I am not able to force the use of the PPAPI
> version
>
> OK after some more trying it appears that Firefox cannot tell
> the NPAPI and PPAPI plugins apart when both are installed
This is because both look like NPAPI plugins to Firefox (which incidentally does not support PPAPI plugins anyway): the PPAPI plugin installed by adobe-flashplugin is wrapped as a NPAPI plugin by browser- plugin- freshplayer- pepperflash. But you (and Firefox) can still tell the difference from the version numbers.
As mentioned in my previous comment, I suggest using Andrei Alin's version of browser- plugin- freshplayer- pepperflash instead of the one in the Ubuntu repository. It will set up the symlinks so that only the wrapped PPAPI plugin is shown to Firefox, not the NPAPI plugin.
> some websites will start the NPAPI plugin and some other will
> run the PPAPI plugin
Are you sure about that? I've always thought only the higher-version plugin was used by Firefox, so, the wrapped PPAPI plugin. I've never seen Firefox start the lower-version plugin when running Flash content on the web, but I'm not checking every time though.
> Disabling one of the plugins does not work either because the
> setting is applied to both plugins (this is visible after
> reloading the plugin setting menu).
Yes, this is irritating. Again, Andrei Alin's version.
> This makes browser- plugin- freshplayer- pepperflash mostly useless plugin- freshplayer- pepperflash and in-nonfree
> and "solves" my both issues, I will just stick to adobe-flashplugin
> and remove browser-
> pepperflashplug
I don't see how this solves anything, and if you do that, your Firefox will use the deprecated 11.2 NPAPI Flash plugin, because you'll have removed the PPAPI/NPAPI wrapper (browser- plugin- freshplayer- pepperflash) .
Now the 11.2 NPAPI plugin is still supported security-wise, so that may be enough for your needs, while waiting for the updated new NPAPI plugin to exit beta.