October Flash Dance

Chromium and Pepper Flash:

chromium_iconChrome was updated last week (I failed to notice because of the crunch mode at work) with a new Flash from Adobe. I had just updated the Chromium package for Slackware last week, but I decided to apply the micro version upgrade anyway.

More detail on the Chrome releases blog for Chromium 38.0.2125.104 – some bugs were fixed but apart from the Flash upgrade in Chrome, not much exciting there. The real heavy lifting was done for last week’s release.

I took the binaries from that new Chrome RPM and used those to update my Slackware package for chromium-pepperflash-plugin. New version is 15.0.0.189.

Linux Flash:

adobe_flash_8s600x600_2 Adobe releases its Flash updates for all platforms, one of them is the “legacy” Linux NPAPI plugin for Mozilla-compatible browsers. See Adobe’s monthly security bulletin for all the version numbers and vulnerabilities. The Linux flashplayer-plugin went up to 11.2.202.411.

 

 

Pipelight with Windows Flash:

pipelight-logoFor my pipelight package, you can easily update the Windows plugins it installed for you earlier (including the Windows Flash player if you use that) by running (as root) the script:

# pipelight-plugin --update

A new package is not required therefore.

 

Eric

7 thoughts on “October Flash Dance


  1. Recently I have compiled and installed FreshPlayerPlugin on all my Slackware machines, for using the Pepper Flash in Firefox.

    It seems to work quite nicely.





  2. Hi Eric, the newest release of Chromium wants to clear the chromium config of the pepperflash and winevide plugins. Do I need to reinstall them so the integrate properly?


  3. BrianA, chromium does not want to do that.
    But it will install a default chromium configuration file as /etc/default/chromium.new.
    As the install script says: “we leave the .new copy for the admin to consider…”. You should always consider if you really need the .new files that get installed with some packages. The “slackpkg new-config” command has a “diff” option to show you the differences between old and new configurationfiles.

    If you overwrote the customized chromium configurationfile then re-installing the chromium plugins is the fastest and easiest solution.


Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.