LinuxQuestions.org - [SOLVED] 32-bit Chromium isn't detecting Pepperflash

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - 32-bit Chromium isn't detecting Pepperflash (https://www.linuxquestions.org/questions/slackware-14/32-bit-chromium-isnt-detecting-pepperflash-4175537078/)

32-bit Chromium isn't detecting Pepperflash

I have Chromium and Pepperflash on a 32-bit Slackware, and Chromium isn't detecting Pepperflash. I don't see it in about:config. Clearing ~/.config/chromium and ~/.cache/chromium didn't help.

Code:

dugan@t23 ~> ls /var/log/packages | grep -i chromium

chromium-41.0.2272.76-i486-1alien

chromium-pepperflash-plugin-17.0.0.134-i386-1alien

chromium-widevine-plugin-41.0.2272.76-i386-1alien

Oddly, if I use upgradepkg to switch to a 64-bit pepperflash package, then I do see it in about:config. The plugin then (as expected) crashes whenever it runs. If I then use upgradepkg to switch back to the 32-bit version (and then of course restart Chromium), then I stop seeing it in about:config.

Has there been a bug in Chromium (upstream) that would prevent it from seeing Pepperflash in a 32-bit build?

Okay, I figured it out. My /etc/default/chromium was borked.

For future reference, what is the procedure for upgrading Chromium and/or Pepperflash so that that file is updated (or not updated, if it shouldn't be) properly?

I intend to move away from the /etc/default/chromium configuration file which can be edited by plugin installation scripts. It's error prone.
My plan is to create a /etc/chromium/ directory and allow the chromium package and its plugins to create their configuration files in there. That way, Chromium's default configuration file will no longer have to be modified.

I want to implement that when Chromium moves up to its next major version.

I don't know why I seem to be the only one having a problem, but I think that that change would be great, and I'm really thankful that you're not only doing great Chromium builds, you're also continuously improving them.