This bug was fixed in the package freshplayerplugin - 0.3.5-1ubuntu3.1
---
freshplayerplugin (0.3.5-1ubuntu3.1) yakkety; urgency=medium
* d/*.postinst, d/*.preinst, d/*.prerm:
- Use the same alternative as the adobe-flashplugin package to
prevent confusion with the NPAPI p
The package is not present in trusty.
A backport request would be possible, though:
https://wiki.ubuntu.com/UbuntuBackports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability
Any chance of fixing this in Trusty? Should be equally trivial to fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability issue with adobe-flashplugin
To manage notifications
I installed browser-plugin-freshplayer-pepperflash 0.3.5-1ubuntu3.1 from
yakkety-proposed and could verify the test case.
** Tags removed: verification-needed
** Tags added: verification-done-yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Hello Niklas, or anyone else affected,
Accepted freshplayerplugin into yakkety-proposed. The package will build
now and be available at
https://launchpad.net/ubuntu/+source/freshplayerplugin/0.3.5-1ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
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 pl
I installed browser-plugin-freshplayer-pepperflash 0.3.4-3ubuntu0.1 from
xenial-proposed and could verify the test case.
** Tags removed: verification-needed
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Hello Niklas, 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.4-3ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new p
I've uploaded this to the -proposed queues for review by the SRU team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability issue with adobe-flashplugin
To manage notifications
@Brian: I don't have the permissions to upload it which is why ubuntu-
sponsors is subscribed...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability issue with adobe-flashplugin
Gunnar - Do you have any plans to upload this to the -proposed queue for
review by the SRU team?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability issue with adobe-flashplugin
Hello Gunnar, thanks for your fix and sorry for my late answer. I tried
your fix and it works as intended, the NPAPI plugin is hidden and
Firefox uses the PPAPI plugin.
https://www.adobe.com/software/flash/about/ show the correct version
number (currently 23.x).
--
You received this bug notificat
** Changed in: freshplayerplugin (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: freshplayerplugin (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: freshplayerplugin (Ubuntu Xenial)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
** Changed in:
This bug was fixed in the package freshplayerplugin - 0.3.5-1ubuntu4
---
freshplayerplugin (0.3.5-1ubuntu4) zesty; urgency=medium
* d/*.postinst, d/*.preinst, d/*.prerm:
- Use the same alternative as the adobe-flashplugin package to
prevent confusion with the NPAPI plugin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: freshplayerplugin (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/163
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: freshplayerplugin (Ubuntu Yakkety)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/16
** Also affects: freshplayerplugin (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: freshplayerplugin (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
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 Ubu
Thanks for taking care of this bug Gunnar.
Unfortunately I can't test your packages since I still use Trusty for
the time being. I did at least compare the contents of your Xenial build
against the one available in multiverse and the one in Andrei Alin's
PPA. It looks good to me and should fix the
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
Title:
Compability issue with adobe-flashplugin
To manage notifications about this bug go to:
https://bugs.launchpad.n
** Description changed:
+ [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
Thanks for those clarifications, Niklas. Just confirmed that it actually
uses adobe-flashplugin's PPAPI plugin, even if the Firefox GUI keeps
showing the fake one.
Then it's a trivial issue, which doesn't jeopardize security, and
nothing that needs to block the proposed fix.
This bug is now in th
See also https://github.com/i-rinat/freshplayerplugin/issues/246
13.1.2.3 is a dummy version used when the wrapper can't find the plugin.
Firefox caches plugin information in pluginreg.dat, and since the
wrapper's doesn't change when adobe-flashplugin is installed, firefox
doesn't notice anything
@Gunnar: This is known issue upstream and is harmless. The version shown
is only used for plugin listing in the browser, the actual version used
is the one provided by adobe-flashplugin. You can verify this at
https://www.adobe.com/se/software/flash/about/
See https://github.com/i-rinat/freshplaye
Proposed changes for Xenial, Yakkety and Zesty have been uploaded to
this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/freshplayerplugin
There is one thing I'm not quite comfortable with: If I install browser-
plugin-freshplayer-pepperflash without adobe-flashplugin being present,
some od
** Changed in: freshplayerplugin (Ubuntu)
Importance: Undecided => High
** Changed in: freshplayerplugin (Ubuntu)
Status: Confirmed => In Progress
** Changed in: freshplayerplugin (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)
--
You received this bug notificati
I agree with everything Niklas said. Two remarks:
1. I'm not sure it's a problem to have two versions of the Flash plugin,
because one is the outdated NPAPI version:
> flashplugin-alternative.so -> /etc/alternatives/mozilla-flashplugin
(installed by adobe-flashplugin)
and the other is the up-to-
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: freshplayerplugin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633678
T
28 matches
Mail list logo
