Main menu:


Please consider a small donation:



Or you can donate bitcoin:


Thanks to TekLinks in Birmingham, AL, for providing colocation and bandwidth.

Page Rank


FOSS Force Best Blog--2013 Award

Recent posts

Recent comments

About this blog

I am Eric Hameleers, and this is where I think out loud.
More about me.


Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 425 other subscribers

My Favourites



April 2019
« Mar    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



Flash security updates too (and chromium on the horizon)

adobe_flash_8s600x600_2 I mentioned “Patch Tuesday” in my previous post and also mentioned Adobe in passing. The reason is, they made new versions available of their Flash Player Plugin for web browsers. Several security issues have been addressed, you can read all about those in their bulletin “apsb14-02

I packaged both the flashplayer-plugin for Mozilla based browsers, and the pepperflash plugin for (Chrome and) chromium. The former is well-known (you can use it with your Firefox) and the second one has been extracted from the Chrome RPM and re-packaged as a plugin for my chromium package for Slackware.

Packages are here:


chromium_icon I am still working on a new chromium 32.0.1700.77 package (the same version as the latest stable version of Chrome) but since the Chromium team have not (yet) released any official source tarball I had to find out how to create such a tarball. The above pepperflash plugin works perfectly with my current chromium-31.0.1650.67 package!

But the finished 64-bit package works OK so far, still testing:

Old:  chromium_about_31.0.1650.67

New: chrome_about_32.0.1700.77  chromium_about_32.0.1700.77

I’ll start the 32-bit SlackBuild after I finish typing.

Oh yeah if you want to package the new google-chrome yourself, you will have to apply this diff to the google-chrome.SlackBuild in the Slackware tree, else your desktop menu icon is fubar:

--- extra/google-chrome/google-chrome.SlackBuild 2012-08-01 20:48:31.000000000 +0200
+++ google-chrome.SlackBuild 2014-01-15 21:34:38.425845534 +0100
@@ -105,9 +105,6 @@
# Install a .desktop launcher:
 sed -i -e "s#Icon=google-chrome#Icon=/opt/google/chrome/product_logo_256.png#" \
- $PKG/opt/google/chrome/google-chrome.desktop
-mkdir -p $PKG/usr/share/applications
-ln -s /opt/google/chrome/google-chrome.desktop \

 mkdir -p $PKG/install

Have fun! Eric



Comment from Mike Langdon (mlangdn)
Posted: January 16, 2014 at 11:24

The link for the chromium-pepperflash-plugin is broken. I had to navigate to your slackbuilds.
But that was a small matter – thanks for the packages! 🙂

Comment from alienbob
Posted: January 16, 2014 at 11:34

Weird… the “http://” prefix was not present in the URL therefore it was just appended to the blog’s URL. I have fixed the link now.


Comment from Eduardo
Posted: January 16, 2014 at 15:15

Great! I will wait for your package Eric.

Comment from Olaus
Posted: January 23, 2014 at 11:54

Is it possible to have booth flash packages installed? I have installed Flash for Mozilla, which seems to be used also in Chromium. If I install pepperflash, will that be used instead of Mozilla-flash in Chromium?

Comment from alienbob
Posted: January 23, 2014 at 15:33

You’ll have to disable one of the two flash plugins. In Chromium, that is possible. Open the special URL chrome://plugins and enable advanced view. Search for Flash and click on “disable” for the plugin that you don’t want to use.


Pingback from Google Chrome Icon
Posted: January 26, 2014 at 20:16

[…] right about it being the best way to learn. See this post on Alien BOB's blog to fix the issue. Regards, […]

Write a comment