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



More Chromium, LibreOffice and Flash updates

That sounds a heck of a lot like another post I wrote recently on this blog…  a little more than two weeks ago. The big guys made a move again, and this is what you get from me as a result.


chromium_iconChromium (and of course Chrome) were updated to version 33.0.1750.149, with 7 security fixes. The Chrome binaries are equipped with an updated Flash Player plugin ( which is also a security upgrade, see below).  These are the highlighted fixes (aka the biggest bounties paid):

  • [$4000][344881High CVE-2014-1700: Use-after-free in speech. Credit to Chamal de Silva.
  • [$3000][342618High CVE-2014-1701: UXSS in events. Credit to aidanhs.
  • [$1000][333058High CVE-2014-1702: Use-after-free in web database. Credit to Collin Payne.

You will find the chromium packages (Slackware 14.1 and -current) here:

I also provide updated packages for chromium-pepperflash-plugin with the Fpash plugin binary taken from the official Chrome distribution.


LibreOffice 4.2.2 (codenamed ‘Fresh’) packages for Slackware 14.1 and -current are ready too. The official announcement  considers LibreOffice 4.2.2 to be “the most feature rich version of the software, and is suited for early adopters willing to leverage a larger number of innovations“. However, the announcement continues with “For enterprise deployments, The Document Foundation suggests the more reliable LibreOffice 4.1.5 “Stable”.” Of course I have LibreOffice 4.1.5 packages, they are built on Slackware 14.0 and work well on Slackware 14.1 and -current. It’s your choice!

Package locations:

Linux Flash Player

As mentioned above in the Chromium section, Adobe released security updates of their Flash Player for all platforms. The Adobe security bulletin shows as the new version for native Linux. Package location:


Note: a new version of pipelight has not yet been released, but if you want your Wine-installed Windows Flash player to be secure and safe as well, you can run the following command (as root – not as your normal user account like I wrongly advised before):

# pipelight-plugin --update

which will update the “/usr/share/pipelight/install-dependency” script. Next time you open a web page which loads pipelight, it will automatically upgrade your Windows Flash player in the wine-pipelight directory to the latest version.

Have fun! Eric


Comment from lems
Posted: March 15, 2014 at 16:06

Hi Eric,

thank you for keeping us up-to-date. However, one question: when I run pipelight-plugin –update’ as user, I get: ERROR: Root rights required to replace dependency-installer script

So I guess you *do* need to run this as root, or did I miss something?


Comment from lems
Posted: March 15, 2014 at 16:26

Hi again,

now it works, I didn’t do anything except for closing and re-opening firefox, but when I run it as user it now says Script dependency-installer is already up-to-date.’

Do I need to run it only once as user, or for every user using pipelight?


Comment from lems
Posted: March 15, 2014 at 16:36

I reinstalled pipelight and tried to run the command as user, this did not work. Looking at the script, it replaces DEPENDENCY_INSTALLER_PATH, which is /usr/share/pipelight/install-dependency.


Comment from alienbob
Posted: March 15, 2014 at 17:19

Yeah you need to run “pipelight-plugin –update” as the root user. I updated the main article.


Comment from John
Posted: March 15, 2014 at 20:57

Cheers Eric
Just finished building libreoffice 4.2.2. I had one problem line # 188 SRCVER=${SRCVER:-4.2.1} must be changed to SRCVER=${SRCVER:-4.2.2}
Built on a i5 3750 with 32 gb of ram with command
time sh libreoffice.Slackbuild
real 100m32.986s
user 316m26.277s
sys 28m50.850s

also if interested the disk usage was
du -hs /mnt/other/tmp
29G /mnt/other/tmp
Probably would be faster if I would use a ramdisk instead of /mnt/other/tmp. Some day I will have to figure out how to do that
PS I was using the computer for other functions while building

Comment from alienbob
Posted: March 15, 2014 at 23:43

Yes I had “forgotten” to upload the libreoffice.SlackBuild to see what would happen 😉

And yes, it is a bitch to build. Chromium is about just as terrible.


Comment from Fred
Posted: March 22, 2014 at 13:41

Sorry I wrongly posted the original message on Libreoffice 3.4.2 announcement.

I get an error message when I try to launch LibreOffice: /usr/sbin/soffice: line 161: /usr/bin64/libreoffice/program/oosplash: cannot execute binary file.

It is a fresh install of Slackware 14.1. On another PC (32 bits), I have no issue.

Comment from alienbob
Posted: March 23, 2014 at 18:02

Hi Fred

That sounds as if you have installed the 64-bit LibreOffice package on a 32-bit Slackware installation…


Comment from Fred
Posted: March 25, 2014 at 13:22


You are probably right 🙁


Comment from hottdogg
Posted: May 5, 2014 at 15:45

Thanks alot for providing updated chromium package. I always use your chromium package in my slackware 🙂

Comment from Stephan
Posted: May 31, 2014 at 14:29

Hi Eric,

I am basically pretty happy with your Chromium package (35.0.1916.114 (270117)). However, I have realized that this version and may be all earlier versions as well do not display German letters like ö, ä, ü, ß. I have tried to use a different encoding but I can not change it in you chromium package. It always falls back to the original setting.

I do not have this issue with other Chrome based browser packages (Iron, Google Chrome).

Do you have any idea how to overcome this little issue in your Chromium package?

Cheers and thanks


Comment from alienbob
Posted: May 31, 2014 at 14:58

Hi Stephan

What does that look like, a page which does not show these accented characters? Do you have a screenshot? Did you set your language to an UTF-8 variant in /etc/profile.d/ ?


Comment from Stephan
Posted: May 31, 2014 at 17:37

Hi Eric,

I would provide a screenshot, but how can I do this. In general I can not type these characters in any search field in Chromium (but it works on the very same internet page, the very same machine and account with Iron and Google Chrome, Firefox, and all other browsers I have installed – but I started liking Chromium a lot (-: ). I can not even use these characters on the Google homepage using Chromium and therefore it does not find appropriate results.

Language setting on my machine is Slackware default: export LANG=en_US

However, since Google Chrome and Iron on the very same machine and user account do accept these German characters in their search fields I thought it has something to do with the package you built (I assumed that you would not consider this special German characters as long as someone friendly asked you to do this). Since changing the encoding in in your latest Chromium package (Tools/Encoding) does fall back to default settings I am out of an idea how to resolve this little issue.

Eric, this is not an urgent issue, it is just a hint that there is maybe something wrong.

Please let me know how I can provide a screenshot.



Comment from bam
Posted: June 3, 2014 at 23:08

Hi Eric,
can’t use java applets in latest chromium-35.0.1916.114, Slackware 14.1. There were no problems in previous version. Any thoughts?

Comment from alienbob
Posted: June 3, 2014 at 23:29

Hi bam

It’s simple really:

Google stopped supporting NPAPI based plugins (aka ‘mozilla-compatible’ plugins) starting with Chrome and Chromium 35. They have announced their intentions a long time ago already, and the Linux platform got hit first. The Windows version of Chrome will support NPAPI plugins a bit longer, until that support too will be removed later this year.

The icedtea developers have not yet decided if they will create a PPAPI plugin for Chrome/Chromium (PPAPI or Pepper Plugin API is the Google variant of a plugin protocol for browsers).

If you need Java or Pipelight in a browser you will have to use Firefox from now on.



Write a comment