pepperflashplugin-nonfree is not updated with google-chrome's plugin version updates
Bug #1507542 reported by
Łukasz Jagielski
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Pepperflashplugin Nonfree |
Invalid
|
Undecided
|
Unassigned | ||
| pepperflashplugin-nonfree (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Because of this user can be left with outdated plugin in his OS, even though google-chrome has a newer version in its newest package.
Revision history for this message
| Hans Hellén (hans-hellen) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in pepperflashplugin-nonfree (Ubuntu): | |
| status: | New → Confirmed |
| Changed in pepperflashplugin-nonfree: | |
| status: | New → Invalid |
To post a comment you must log in.
Yes, it is not very clearly stated or warned that the user of this package has to manually update the plugin by commanding:
update-
Or do you mean that although a new version has been released a couple of days ago, still the plugin are not updated because it is not "verified" by the packaged maintainer(s), what ever it means. Check:
http://
that is where the updates are being checked. Currently it says 19.0.0.245.
https:/
currently 20.0.0.228.