[Bug 1633678] Re: Compability issue with adobe-flashplugin

Gunnar Hjalmarsson 1633678 at bugs.launchpad.net
Fri Oct 28 21:53:30 UTC 2016


On 2016-10-28 22:07, Nathanaël Naeri wrote:
> One point of detail: it looks like you made your Xenial package from
> the Debian or Alin one and your Yakkety/Zesty packages from the
> Ubuntu ones.

For Xenial there is no Ubuntu/Debian delta, so I made all of them based
on what's currently in the Ubuntu archive. That's how you normally do it
to have an update of a stable release accepted: Settle for the changes
needed to address the bug in question.

> This shows in the Maintainer and Original-Maintainer fields of
> d/control, but that's the only difference AFAICT.

Ouch.. You made me realize that I forgot to change the Maintainer field
in the Xenial proposal. Fixed now.

-- 
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:
  [Impact]

  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.

  Proposed changes to achieve this are available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/freshplayerplugin

  [Test Case]

  1. Install adobe-flashplugin from Canonical Partner.
  2. Install the current version of
     browser-plugin-freshplayer-pepperflash.
  3. Restart Firefox and find that two version of "Shockwave Flash" are
     shown under Tools -> Add-ons -> Plugins.
  4. Install the proposed browser-plugin-freshplayer-pepperflash.
  5. Restart Firefox and find only adobe-flashplugin's PPAPI plugin under
     Plugins.

  [Regression Potential]

  Low. This proposal is a natural step for Ubuntu to deal with the
  pepperflashplugin-nonfree breakage caused by Google. As an extra
  bonus, since adobe-flashplugin actually installs the PPAPI plugin and
  not just downloads it from an external source at install, users will
  have the (almost) latest plugin version installed through the package
  updates.

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