I'm in Xubuntu LTS, Google Chrome stable latest.
I have been using Xubuntu without Adobe Flash package for quite some time, and things works fine.
Then this one day, for some reason I don't remember, I installed the legacy Flash Player package (I think it's
flashplugin-installer?), and suddenly ALL blink-based browsers (Google Chrome, Opera, Vivaldi) lost Flash Player in their plugin setting page, and can not play Flash contents.
So I Googled, installed
pepperflashplugin-nonfree instead, and Flash plugins returned -- except for Google Chrome.
Now in my Chrome, all flash contents will show a warning "Adobe Flash Player is out of date" (even if I disable Flash Player in chrome://plugins), and Chrome refused to play them.
Some version info:
- Current Xubuntu version: 16.04.01
- Current Flash Player version: 22.214.171.124
- In chrome://plugins
Adobe Flash Player - Version 126.96.36.199
Type: PPAPI (out-of-process)
- In chrome://components
Adobe Flash Player - Version 0.0.0.0
- In chrome://version
Google Chrome: 54.0.2840.100 (Official Build) (64-bit)
If, however, I do this:
sudo ln -s /usr/lib/adobe-flashplugin/ /opt/google/chrome/PepperFlash # There's no PepperFlash folder by default
then chrome://components will show
Adobe Flash Player - Version 188.8.131.52
But chrome://plugins and chrome://version still show
184.108.40.206, and Flash contents still show the "out of date" warning and Chrome still refuse to play them.
I've tried uninstalling and reinstalling Chrome with no avail. Any way I can fix this?
It seems this relates to how Google Chrome distribute Flash Player in version 54+, so I used the "Check for update" button in chrome://components, and it says
But eventually says
Component not updated
Linking everything from
~/.config/google-chrome/PepperFlash/ didn't seem to help.
It seems Chrome insist on using proxy
"DIRECT" when it checks for component update (
https://clients2.google.com/service/update2?cup2key=..., see it in
chrome://net-internals/#events), despite me setting PAC proxy in
dconf and Chrome extension, so our lovely GFW happily blocked the request. Found a VPN and the component successfully upgraded.