*Wed Nov 20 9:13AM PST 2014 *Fix: Chromium Browser 20x-30x+ versions *Issue: Plugin Support removed for flash *Symptom: Flash no longer working after an update to either chrome or chromium often causing youtube issues as not all videos are html5 converted, software based phone apis (couple of these like twilio or Tropo) *Update issue: External Plugins: Flash SOLUTION *System: Ubuntu 12.04.4 x86_64 Multi-Arch
The Chrome and Chromium Teams are so far removing the plugin not the architecture from Chromium. So if you can grab a new chrome compile for the same system and let Chromium know the exact path with a couple other minimal configs, you can not only keep it, you can update and maybe largely improve on its working condition, while solving certainly the problem at hand. Pickup a recent Mozilla copy just to keep options open and take the ego down notch at google.
Dont go update/downdate and or modify your scope of repos, dig into your configs based on speculative assumptions on the forums, unless you know what you are doing. If you have an extensive knowledge hacking chrome-os fine but and when I started on the hunt for answers there was nothing but bad advice, NOBODY I could find had the right answer, which in itself was scary. Also major changes between versions and channels, dramatically affect file paths. I was so desperate because my browser phones wouldnt run and sometimes well you wouldnt believe what can happen when you don't come to the phone.
Caution Doing this wrong especially following the blogs and can equal an apt-F***up. Official word is that it's permanent, there is no offered solution for 12x Ubuntu though there is for the moment 14.4 as a Trusty package of pepperflash supposedly resolves the issue. Really though one need only acquire a simple .so file and modify and/or create the settings files no-installs, dpkg'ing, easily reversible.
First, make a BACKUPPPPPPPPPPPPPP of chrome, chromium, your system, your personal settings, like bookmarks history, etc I run my user profile directories out of /var/tmp/[chrome,firefox]/profiles/[1,2,3,...] I always try to avoid giving any vendor the control to update, wipe out, or modify my data. If I uninstall chrome totally, I still have what I need.
Flash sucks in every way, but I need it for like two things, non-negotiable stuff. If you do too atleast in transition this has worked in multiple instances across multiple Chromium versions ranging from 20 to 31, all successfully accepted multiple versions of PepperFlash, most recently this one:
Chromium 31.0.1650.63 (Developer Build 31.0.1650.63-0ubuntu0.12.04.1~20131204.1) Ubuntu 12.04
OS Linux
Blink 537.36 (@163124)
JavaScript V8 3.21.18.13
Flash 15.0.0.223
User Agent Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/31.0.1650.63 Chrome/31.0.1650.63 Safari/537.36
###November-19-2014 ###*Pepperflash Version: 15.0.0.223 Replace/modify current CHROMIUM_FLAGS Options to the below information according to YOUR path and YOUR version of PepperFlash, wherever it may be.
nano /etc/chromium-browser/default
add or modify the below line, create the folder and file if they don't exist:
CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=/opt/google/chrome-unstable/PepperFlash/libpepflashplayer.so --ppapi-flash-version=15.0.0.223"
####*Pepperflash Version: 15.0.0.223
**note:bundled with Chrome-unstable ubuntu 64 *OS: 12.04.4 Ubuntu / chrubuntu / Raybuntu ;) *ver chrome: approx 40x **(current repo past 24 hours install)
###Pepperflash Manifest snippet most recent:
"description": "Pepper Flash Player",
"name": "Flapper",
"version": "15.0.0.223",
"x-flapper-revision": "6114",
"x-ppapi-arch": "x64",
"x-ppapi-os": "linux",
For the .so file, use the most recent one you already have. Changing the above files was all it took for me but it will crash if you use the wrong numbers. The path will be something along the lines of
/opt/google/chrome/pepper/libpepflashplayer.so
/opt/google/chrome/pepper/pepper-flash.info
I juggle canaries, betas, old stables, devs, on a handful of hacked Acer C7's and USB ROMs and its got some definite frustrations but still the best. Please dont use DEV if you are not a Dev. Chrome is a truly fascinating place to begin or update your knowledge of browser technology, well worth devoting the study time if you are up to it. If not, go with stable.
solution by: Ray Anthony source
Wed Nov 20 9:13AM PST 2014