group.of.nepali.translators team mailing list archive

[Launchpad Bug Tracker <1633678@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package freshplayerplugin - 0.3.4-3ubuntu0.1

---------------
freshplayerplugin (0.3.4-3ubuntu0.1) xenial; urgency=medium

  * d/*.postinst, d/*.preinst, d/*.prerm:
    - Use the same alternative as the adobe-flashplugin package to
      prevent confusion with the NPAPI plugin installed by
      adobe-flashplugin (LP: #1633678).
      Thanks to Alin Andrei for the solution!
  * d/control:
    - Drop the pepperflashplugin-nonfree recommend.
    - Recommend adobe-flashplugin.
    - Maintainer: Ubuntu Developers.
  * d/rules:
    - Run tests with LC_ALL=C to prevent the build failure reported in
      LP bug 1578252.

 -- Gunnar Hjalmarsson <gunnarhj@xxxxxxxxxx>  Fri, 28 Oct 2016 23:00:00
+0200

** Changed in: freshplayerplugin (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1633678

Title:
  Compability issue with adobe-flashplugin

Status in freshplayerplugin package in Ubuntu:
  Fix Released
Status in freshplayerplugin source package in Xenial:
  Fix Released
Status in freshplayerplugin source package in Yakkety:
  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