Review your favorite Linux distribution.
Go Back > Blogs > linux-related notes
User Name


Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
Rate this Entry

Chromium/chrome adobe flash player. That was confusing

Posted 06-18-2016 at 02:47 PM by the dsc

I was trying to install flashplayer on chromium by symlinking with chrome's flashplayer, then I found out that you actually need to point out as flags something like "flashplayerpath=path" and also a version flag for some reason. Somewhere it was suggested that you could add it to a /etc/chromium-browser/default file that exists, and by deafult does nothing, but has a "CHROMIUMFLAGS" variable "set as empty".

Then I came up with a grep/sed line to get the version from chrome's manifest.json, and added prior and 'within" to that variable, so I'd not need to update it manually every time.

But for some reason, even though chrome://plugins on chromium would say flash is there (with the correct version), it wouldn't work anywhere.

Then I ended up trying a ubuntu/debian package "pepperflash-nonfree" or something, which I was avoiding as it would download chrome again, just to get the a single file I already had. And somehow it worked! I even read somewhere that you don't need to bother with changing flash-version in any flag file, and I thought, "wow, how do they do that? It's basically the same browser, I don't get why what I did didn't work".

And I found out it was virtually the very same thing! It was just in a different ".d" type of file placement, at /etc/chromium-browser/customizations.

But the crucial difference is that the package's flagging includes the actual .so file at the end of the path, not "just the path" ("folder"), as I had it... doh!

My version of things and the package's version:

version=$(grep version /opt/google/chrome/PepperFlash/manifest.json | sed 's|.*"version": ||;s|"||g;s|,||')
CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=/opt/google/chrome/PepperFlash/LIBPEPFLASHPLAYER.SO-SHOULD-BE-HERE --ppapi-flash-version=$version"
flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f 2 | sed -e "s/,/./g"`
CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso --ppapi-flash-version=$flashversion"
The latter wasn't actually /opt/google/chrome originally, but somewhere else.

Now chrome doesn't need to be downloaded twice, if ever, as it has an internal update mechanism that downloads only flash.

Until this thing exists.

It was funny watching a "tutorial" for a similarly described problem on MS® Windows® ("couldn't load the plugin"), when the guy not only deletes the flash folder but already empties the trash bin... just in case it's still running over there, you know. He probably didn't realize it was running youtube on HTML5 then, it didn't really solve the flash issue itself...
Posted in Uncategorized
Views 900 Comments 0
« Prev     Main     Next »
Total Comments 0




All times are GMT -5. The time now is 12:56 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration