Comment 2 for bug 1633678

I agree with everything Niklas said. Two remarks:

1. I'm not sure it's a problem to have two versions of the Flash plugin, because one is the outdated NPAPI version:

> flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin (installed by adobe-flashplugin)

and the other is the up-to-date PPAPI version wrapped by freshplayerplugin to look like a NPAPI plugin:

> flash-mozilla.so -> /etc/alternatives/flash-mozilla.so (installed by browser-plugin-freshplayer-pepperflash)

and I'm pretty sure that the browser uses the version with the highest version number. Still, it's messy.

2. Andrei Alin's version 0.3.6-1 of browser-plugin-freshplayer-pepperflash (ppa:nilarimogard/webupd8) fixes that issue:

> browser-plugin-freshplayer-pepperflash should use the same
> alternatives-link as the official package but with an higher
> priority, which would eliminate the compability issue.

> Also the recommend of pepperflashplugin-nonfree should be
> removed and solely recommend adobe-flashplugin instead.

It does exactly that (thanks Andrei). However Ubuntu's version of browser-plugin-freshplayer-pepperflash comes from Debian, and adobe-flashplugin isn't available in Debian, so I wouldn't hold my breath for any compatibility issue with adobe-flashplugin to be fixed in the original Debian package.

I recommend using Andrei Alin's version of browser-plugin-freshplayer-pepperflash.