[Bug 1778041] Re: browser-plugin-freshplayer-pepperflash broken

[Rinat]

> This will leave these binary packages installed on users' systems.
What if there's a future security update that address vulnerabilities in
them?

They were not functional in the first place. Both were just an
experiment hidden behind a switch, which was off by default. Also there
is no much sense in developing them to a working state, since Firefox
dropped any plugins other than Flash. They'll just be ignored by the
browser.

So, most probably, there won't be any updates for -libpdf and -nacl.

> Another option might be to turn them into empty packages.

That would be nice. It's better to have them removed, since some other
browsers could still load other plugins. And if for some reason some
future update reintroduces those plugins again, updates would be easier.
I guess with Break/Replace it will be trickier.

-- 
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/1778041

Title:
  browser-plugin-freshplayer-pepperflash broken

Status in freshplayerplugin package in Ubuntu:
  Fix Committed
Status in freshplayerplugin source package in Xenial:
  In Progress
Status in freshplayerplugin source package in Bionic:
  Fix Committed
Status in freshplayerplugin package in Debian:
  New

Bug description:
  [Impact]

  browser-plugin-freshplayer-pepperflash prevents sites which require
  Flash from working with the latest versions of Firefox. If you select
  "Ask to Activate" in FF, the contents requiring Flash is not shown. If
  you select "Always Activate", the tab with the page requiring Flash
  simply crashes.

  Issue identified via <https://askubuntu.com/q/1048357>. A "no change
  rebuild" does not help.

  The proposed version in the PPA fixes the issue, so the wrapper works
  as intended also with the latest FF version.

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

  This suggests an upgrade to a newer upstream version. This is the
  upstream changelog:

  2017-12-23  Rinat Ibragimov  <ibragimovrinat at mail.ru>

   * release v0.3.9
   * network: stop using files with NPN_PostURL

  2017-12-09  Rinat Ibragimov  <ibragimovrinat at mail.ru>

   * release: v0.3.8
   * misc: add NPN_PluginThreadAsyncCall emulation for Firefox 58

  2017-05-31  Rinat Ibragimov  <ibragimovrinat at mail.ru>

   * release: v0.3.7
   * graphics: add more fullscreen _NET_WM controls
   * misc: drop libpdf wrapper
   * misc: drop NaCl wrapper
   * misc: search for PepperFlash in Chrome component update
   directories

  2016-10-05  Rinat Ibragimov  <ibragimovrinat at mail.ru>

   * release: v0.3.6
   * graphics: fix off-by-one pixel issue in fullscreen scaling
   mode
   * graphics: try to flicker less
   * misc: use ICU for character set conversion, use WhatWG
   canonical encoding name conversion
   * misc: guess default character encoding from locale name
   * misc: guess GTK+ major version at run time

  Admittedly it includes a few minor improvements, but hopefully this
  can still pass as an SRUable microrelease (or something...).

  [Test Case]

  1. Install adobe-flashplugin and the {xenial,bionic}-release
     version of browser-plugin-freshplayer-pepperflash.

  2. (Re)start Firefox and visit
     <https://helpx.adobe.com/flash-player.html>.

  => Find that it doesn't confirm that Flash is installed.

  3. Install browser-plugin-freshplayer-pepperflash from
     {xenial,bionic}-proposed.

  4. Repeat 2.

  => Confirmation that the latest Flash version is installed.

  [Regression Potential]

  Considering that the {xenial,bionic}-release version of
  browser-plugin-freshplayer-pepperflash breaks Flash completely on
  Firefox, the risk that this upload makes the situation worse is
  non-existent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freshplayerplugin/+bug/1778041/+subscriptions