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.

When starting chromium from terminal I get an error message related to sandbox:
Since pepperflash is expected to run sandboxed, could this explain why the plugin doesn't work?

Debian has a bug report

https://bugs.debian.org/cgi-bin/bugr...cgi?bug=918433

Yeah, found this bug report too. But since it's from January I would have expected it to be addressed in later versions. For good measure I also tried
but no difference.

1 members found this post helpful.

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...

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
};

std::string strExpectedArch = "ia32";
#if ADDRESS_SIZE == 64
strExpectedArch = "x64";
#endif

for( int i = 0; pathChecks[i]; ++i )
{
std::string strPath = pathChecks[i];
std::string strManifest = strPath + "manifest.json";
std::string strPlugin = strPath + "libpepflashplayer.so";
if( !LLFile::isfile( strManifest ) )
continue;
if( !LLFile::isfile( strPlugin ) )
continue;

std::ifstream file;
file.open( strManifest, std::ios::in );
if( !file.is_open() )
{
LL_WARNS( "Flash" ) << "Cannot open " << strManifest << LL_ENDL;
continue;
}

Json::Value root;
Json::Reader reader;
if (!reader.parse(file,root))
continue;

std::string strArch; // ia32 or x64
std::string strVersion;

if( root.isMember( "version" ) )
strVersion = root[ "version" ].asString();
if( root.isMember( "x-ppapi-arch" ) )
strArch = root[ "x-ppapi-arch" ].asString();

if( strExpectedArch != strArch )
{
LL_WARNS( "Flash" ) << "Arch mismatch expecting: " << strExpectedArch << " got: " << strArch << LL_ENDL;
continue;
}

LL_INFOS( "Flash" ) << "Arch: " << strArch << " version: " << strVersion << " plugin " << strPlugin << LL_ENDL;

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

I applied a patch in my chromium.SlackBuild which fixes the crash of the plugin when it runs on a system with glib 2.29.
See http://www.slackware.com/~alien/slac...ibc-2.29.patch

1 members found this post helpful.

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.

Ah, so that's the explanation. Thanks a lot for that.