documentation-packages team mailing list archive
Mailing list archive
[Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
Nominated and approved (the latter via a workaround...)
On 2017-02-14 21:40, Naël wrote:
> @Gunnar: Yes, probably too late for Zesty. Besides, we should
> probably leave the package in Zesty for now, if it is to be
> backported to the previous releases via SRUs. We'll make the request
** Also affects: ubuntu-docs (Ubuntu)
** Also affects: ubuntu-docs (Ubuntu Xenial)
** Also affects: pepperflashplugin-nonfree (Ubuntu Xenial)
** Also affects: ubuntu-docs (Ubuntu Yakkety)
** Also affects: pepperflashplugin-nonfree (Ubuntu Yakkety)
** Also affects: ubuntu-docs (Ubuntu Trusty)
** Also affects: pepperflashplugin-nonfree (Ubuntu Trusty)
** No longer affects: ubuntu-docs (Ubuntu Yakkety)
** No longer affects: ubuntu-docs (Ubuntu Xenial)
** No longer affects: ubuntu-docs (Ubuntu Trusty)
** No longer affects: ubuntu-docs (Ubuntu)
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
Package is broken since Google stopped shipping Flash with Chrome 54
Status in pepperflashplugin-nonfree package in Ubuntu:
Status in pepperflashplugin-nonfree source package in Trusty:
Status in pepperflashplugin-nonfree source package in Xenial:
Status in pepperflashplugin-nonfree source package in Yakkety:
Status in pepperflashplugin-nonfree package in Debian:
Pepperflashplugin-nonfree is a Debian package, slightly modified for
Ubuntu, and available in multiverse, that downloads the PPAPI Flash
plugin from Google (up to v1.8.3 in Debian and v1.8.2+nmu1ubuntu1 in
Ubuntu 16.10) or Adobe (starting with v1.8.3+nmu1 in Debian and
v1.8.3+nmu1ubuntu1 in Ubuntu 17.04), and installs it as /usr/lib
Versions that download the PPAPI plugin from Google are currently
broken since Google decided to unbundle the plugin from Chrome 54,
released in late 2016-10. Until that date, ripping the PPAPI plugin
from a download of Google Chrome (which comes as a .deb package) was a
popular way to get it, and the only possible way on Linux in the early
days of the PPAPI plugin, when it was only available to Google. Then
Adobe made the Linux PPAPI plugin available to Canonical and on their
The Debian package was changed to download the plugin from Adobe, in
version 1.8.3+nmu1 on 2017-01-14, and that fix landed in
1.8.3+nmu1ubuntu1 in Ubuntu 17.04 (the current development release) on
The package is still broken in the published releases: 16.10 16.04
14.04. It could be repaired by merging the changes made between
1.8.3ubuntu1 and 1.8.3+nmu1ubuntu1 into the published releases'
versions of the package.
This would qualify for an SRU because the bug comes from a change in a
web service that made the package stop being installable. This change
also causes a security vulnerability in so far as the Flash plugin can
no longer be updated (updates were processed by downloading a new
version of Google Chrome and extracting the bundled Flash plugin).
On Ubuntu < 17.04, installation and reinstallation of
pepperflashplugin-nonfree (v < 1.8.3+nmu1ubuntu1) fails. On Ubuntu
17.04 (v = 1.8.3+nmu1ubuntu1), it succeeds.
I can't think of any. The new version has been in Debian Sid for one
month without any report of a regression, so that's a good sign. It
was initially tested in debbug 833741.
[Why not to SRU]
On the one hand, it's bad form to leave an utterly broken package in
the published releases when it has been fixed in the development
release and works there. Theoretically, SRUs should be performed.
On the other hand, pepperflashplugin-nonfree is The Debian's Way to
install the PPAPI Flash plugin. Ubuntu users are recommended to
install adobe-flashplugin from Canonical's partner repository instead.
Not all Ubuntu users are aware of that. See:
We can consider intentionally not fixing that package in the published
releases, in which case this bug report should be marked Won't Fix in
Yakkety, Xenial, Trusty.
To manage notifications about this bug go to: