** Changed in: freshplayerplugin (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778041
Title:
browser-plugin-freshplayer-pepperflash broken
To manage
This bug was fixed in the package freshplayerplugin -
0.3.9-0ubuntu0.16.04.1
---
freshplayerplugin (0.3.9-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream release (LP: #1778041)
* debian/browser-plugin-freshplayer-libpdf.install:
*
Verified the test case using browser-plugin-freshplayer-pepperflash
0.3.9-0ubuntu0.16.04.1 from xenial-proposed.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a
Hello Gunnar, or anyone else affected,
Accepted freshplayerplugin into xenial-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/freshplayerplugin/0.3.9-0ubuntu0.16.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing
After some discussion we decided to just let the package in as is.
Releasing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778041
Title:
browser-plugin-freshplayer-pepperflash broken
To manage
This bug was fixed in the package freshplayerplugin -
0.3.9-0ubuntu0.18.04.1
---
freshplayerplugin (0.3.9-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1778041)
* debian/patches/typo-from-lintian.patch:
- Dropped; applied upstream.
*
This bug was fixed in the package freshplayerplugin - 0.3.9-0ubuntu3
---
freshplayerplugin (0.3.9-0ubuntu3) cosmic; urgency=medium
* debian/control:
- Only build amd64 and i386.
* debian/patches/use-AV_-prefixed-macros.patch:
- Prevent build failure with ffmpeg 7:4.0.2.
Posting the address to an IRC discussion with Robie last Wednesday:
https://irclogs.ubuntu.com/2018/08/15/%23ubuntu-devel.html#t16:55
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778041
Title:
When I reviewed the bionic package my assumption is what Rinat
mentioned: the removed packages were broken and unusable in the current
state, so no security uploads would be happening anyway. That being
said, maybe adding a breaks would be indeed a good idea since otherwise
users will be left with
> 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
> which kind of d/control entries you have in mind
https://wiki.debian.org/PackageTransition case 6 or 11 perhaps?
I'm not sure either. It occurs to me now that perhaps if the plugins are
completely broken and won't be restored, then there will never be any
need to be able to update them anyway.
Hi Robie,
Addressing that makes sense, I suppose. Not sure, though, which kind of
d/control entries you have in mind, considering that they are not
replaced by anything.
Please note that browser-plugin-freshplayer-pepperflash is not built on
all architectures, so in that case we may want to
+ * debian/rules:
+- libpdf and NaCl wrappers dropped upstream, so dropping the
+ browser-plugin-freshplayer-libpdf and
+ browser-plugin-freshplayer-nacl binaries.
This will leave these binary packages installed on users' systems. What
if there's a future security update that
No problem with the version number, of course.
Verified the test case using browser-plugin-freshplayer-pepperflash
0.3.9-0ubuntu0.18.04.1 from bionic-proposed.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you
If you don't mind I have modified the version number to follow the
security team's versioning scheme. There was nothing wrong with the
previous versioning - I prefer if that kind of versioning is used for
direct backports to series where other versioning schemes wouldn't quite
cut it.
--
You
Hello Gunnar, or anyone else affected,
Accepted freshplayerplugin into bionic-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/freshplayerplugin/0.3.9-0ubuntu0.18.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing
Successfully built on cosmic. Still in -proposed, though, awaiting the
migration of the latest ffmpeg.
** Changed in: freshplayerplugin (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Rebuild with upgraded ffmpeg failed:
https://launchpad.net/ubuntu/+source/freshplayerplugin/0.3.9-0ubuntu2
Attached new debdiff with a cherry picked upstream commit to handle
that.
** Patch removed: "freshplayerplugin_cosmic.debdiff"
The Cosmic build failed for s390x, which prevents migrating to cosmic-
release. OTOH, the browser-plugin-freshplayer-pepperflash package is a
wrapper to be used together with the PPAPI plugin in adobe-flashplugin,
which is only built for amd64 and i386. So let's only build the package
for amd64
** Also affects: freshplayerplugin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: freshplayerplugin (Ubuntu Xenial)
Status: New => In Progress
** Changed in: freshplayerplugin (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: freshplayerplugin
** Changed in: freshplayerplugin (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778041
Title:
browser-plugin-freshplayer-pepperflash broken
To manage
** Bug watch added: Debian Bug tracker #902256
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902256
** Also affects: freshplayerplugin (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902256
Importance: Unknown
Status: Unknown
--
You received this bug
** Description changed:
[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
** Changed in: freshplayerplugin (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: freshplayerplugin (Ubuntu Bionic)
Status: New => In Progress
** Changed in: freshplayerplugin (Ubuntu Bionic)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received
** Also affects: freshplayerplugin (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778041
Title:
browser-plugin-freshplayer-pepperflash
@Naël and @Niklas: Would appreciate to know if you see the same issue as
I do, an whether you think that the proposed upgrade to version 0.3.9 is
a decent way to fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
+ [Impact]
+
browser-plugin-freshplayer-pepperflash prevents sites which require
- Flash from working. 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
It works with Firefox 56.0; there are reasons to assume that browser-
plugin-freshplayer-pepperflash lacks support for Firefox's improved
sandboxing feature.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached please find some terminal output from the crash case ("Always
Activate") when starting Firefox from command line.
** Attachment added: "firefox-terminal-output.txt"
29 matches
Mail list logo
