pepperflash plugin no longer works in chrome-based browsers
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Rep:
pepperflash plugin no longer works in chrome-based browsers
I probably shouldn't bother, since flash is on its way out,and rarely used, but I wonder what has happened lately...
I have Eric's pepperflash plugin package installed. It has worked fine with chromium and vivaldi in the past, but lately it doesn't:
I open a web page with flash content (e.g https://helpx.adobe.com/flash-player.html ) I click the padlock in the URL bar, choose "Allow", reload, and see a box with the message "Right-click to run Adobe Flash Player". (This, by the way, is something new - earlier the flash content was activated immediately).
I right-click, choose "Run this plugin"... and nothing happens.
I've tried downgrading to earlier versions of the PPAPI plugin as well as of Vivaldi, but no difference.
Works here on Slackware 14.2, using my latest chromium and chromium-pepperflash-plugin packages.
However, it does not work on Slackware64-current using those exact same versions of the packages, despite reacting to all the "block by default" and "ask first" messages and settings.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Original Poster
Rep:
Quote:
Originally Posted by tramtrist
Yikes.. I was using this for Slingbox embedded player... Darn
Not familiar with Slingbox, but if it runs in mozilla-based browsers (firefox, icecat and so on) I guess that could be a workaround since the NPAPI plugin still works on -current.
It's really intriguing that (as Eric reported) the PPAPI plugin works under slackware 14.2 so this seems to be a -current only issue. And since it has worked earlier I suspect that some -current upgrade during the last two weeks or so is the reason. But there are more than 100 upgrades to choose from...
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,070
Original Poster
Rep:
With Eric's last chromium version, the pepperflash plugin runs again in Chromium - but not in Vivaldi. So, presumably, something has changed in the chromium code? I wonder if this will affect the next Vivaldi version, too...
works great on my CEF3 bulds. And the headless Dullahan project. my build of Opera. you want to look into how pepper-flash is called. browsers other than google-chrome such as chromium opera new safari new edge etc etc. look in /etc
snippet how we implement it in a plugin in gaming
[CODE]// <FS:ND> try to autodected installed pepper flash (Chrome)
void exportFlashVars()
{
if( getenv( "FS_FLASH_PLUGIN" ) && getenv( "FS_FLASH_VERSION" ) ) // User already set those enviroment variables in their shell or in the firestorm launcher
return;
char const* pathChecks[] = {
"/usr/lib64/chromium-browser/PepperFlash/", // Gentoo
"/usr/lib32/chromium-browser/PepperFlash/", // Gentoo
"/opt/google/chrome/PepperFlash/", // Mint 17.3 / XBuntu 14.04, probably works with all Ubuntu flavors of that version.
"/usr/lib/chromium/PepperFlash/", // Slackware
"/usr/lib64/chromium/PepperFlash/", // Slackware
"/opt/secondlife-install/PepperFlash/", // In case someone likes to extract pepperflash from a chrome installer on their own, give them a choice with a predef. directory
NULL
};
setenv( "FS_FLASH_PLUGIN", strPlugin.c_str(), 0 );
setenv( "FS_FLASH_VERSION", strVersion.c_str(), 0 );
break;
}
}
// </FS:ND>/CODE]
this will show you how and what the browser does to find the location of plugin and version.
On chromium install it is called through a script that is located in /etc
With Eric's last chromium version, the pepperflash plugin runs again in Chromium - but not in Vivaldi. So, presumably, something has changed in the chromium code? I wonder if this will affect the next Vivaldi version, too...
Your computers run Slackware 14.2, right? So they run with an older version of glibc (older than 2.29) and then the crash of the plugin does not occur.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.