[Bug 1633678] Re: Compability issue with adobe-flashplugin
Gunnar Hjalmarsson
1633678 at bugs.launchpad.net
Thu Oct 27 12:20:07 UTC 2016
Thanks for those clarifications, Niklas. Just confirmed that it actually
uses adobe-flashplugin's PPAPI plugin, even if the Firefox GUI keeps
showing the fake one.
Then it's a trivial issue, which doesn't jeopardize security, and
nothing that needs to block the proposed fix.
This bug is now in the sponsorship 'queue':
http://reqorts.qa.ubuntu.com/reports/sponsoring/
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability issue with adobe-flashplugin
Status in freshplayerplugin package in Ubuntu:
In Progress
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1633678/+subscriptions
More information about the Ubuntu-sponsors
mailing list