[Bug 1633678] [NEW] Compability issue with adobe-flashplugin

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Gunnar Hjalmarsson (gunnarhj):

Since google no longer bundles its pepperflash plugin with chrome's debs
(bug #1632870) the recommended way to get the plugin is by installing
adobe-flashplugin from the partner repository. However, since it also
includes the outdated NPAPI-plugin this will result in two flash-plugins
being installed to Firefox' plugin directory, due to the fact that
browser-plugin-freshplayer-pepperflash and adobe-flashplugin doesn't use
the same alternative link, which they should.

In /usr/lib/mozilla/plugins there's currently two links:
flash-mozilla.so -> /etc/alternatives/flash-mozilla.so (installed by browser-plugin-freshplayer-pepperflash)
flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin (installed by adobe-flashplugin)

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.

** Affects: freshplayerplugin (Ubuntu)
     Importance: High
     Assignee: Gunnar Hjalmarsson (gunnarhj)
         Status: In Progress

-- 
Compability issue with adobe-flashplugin
https://bugs.launchpad.net/bugs/1633678
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.