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 426 other subscribers

My Favourites

Online me



May 2019
« Apr    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current



Chromium 60 packages available

chromium_iconGoogle released chrome/chromium 60.0.3112.78 on 25 July. My mother-in-law passed away which shifted my priorities this week, but I found some time to compile new packages. In my VM, the 64bit package creation took more than 24 hours… perhaps now is a good time to look at that Ryzen CPU and empty my savings account. This is getting ridiculous.

Note that this is a security release, fixing 40 security issues. Of those, the following are classified as “high risk” (many of them do not yet have their details published at or CVE-2017-5091, CVE-2017-5092, CVE-2017-5093, CVE-2017-5094, CVE-2017-5095, CVE-2017-5096, CVE-2017-5097, CVE-2017-5098, CVE-2017-5099. So I guess you better do the upgrade.

Compiling Chromium requires ninja and nodejs for which I have packages in my repository if you need them. Fortunately ninja and nodejs are only needed for the compilation, not for actually running the browser.

The packages for chromium, and the Widevine CDM plugin (package is called ‘chromium-widevine-plugin‘), are available for Slackware 14.2 and -current in my repository or one of its mirrors:

Have fun! Eric


Comment from Eduardo
Posted: July 30, 2017 at 00:40

Thank you Eric!
My condolences on the passing of your mother-in-law.

Comment from Andy
Posted: July 30, 2017 at 04:40

Switch to lxc, it has zero overhead. Much faster than a VM.

Comment from Gérard Monpontet
Posted: July 30, 2017 at 09:02

My condolences, also.

Comment from alienbob
Posted: July 30, 2017 at 12:25

LXC is a light container solution which is fine for protecting the host from services you are running on it, but if you are still running the host kernel.
If you really want a 100% clean solution for compiling software for older Slackware releases (I create packages for as old as Slackware 13.37) you need a VM.

Pingback from Links 30/7/2017: Flathub, Jolla Tablet Refunds, Cutelyst 1.8.0 | Techrights
Posted: July 30, 2017 at 18:09

[…] Chromium 60 packages available […]

Comment from Aleksandar
Posted: July 31, 2017 at 17:16

For some reason, this update gives me blury fonts (both interface and content)? (32bit version)

Any ideas how to fix this?

Comment from kjhambrick
Posted: August 1, 2017 at 00:52

Eric —

My thoughts and prayers go out to you and your wife on the passing of your mother-in-law.

— kjh

Comment from Thomas Løcke
Posted: August 1, 2017 at 17:05

This release does weird stuff with font rendering, compared to 59. This on Slackware 14.2 x86_64.

Comment from Drakeo
Posted: August 2, 2017 at 23:18

Thanks for the build Eric. I have spent the last week trying to build other chromium products. So I can understand the frustration of waiting sever hours to see a build fail.
In your case like a days worth with your older system.
I hope one day like here at campus compile on virtual machines running on Blue Waters. When ninja can stack a 10,000 at a time :). Then I woke up :).

Comment from Azirek
Posted: August 6, 2017 at 23:35

Hello. Will you prepare build i486 for Slackware 14.1?

Comment from alienbob
Posted: August 7, 2017 at 10:24

Hi Azirek – probably not. Compiling Chromium just takes too long on my current hardware: more than a day, during which I can not compile anything else.
Perhaps for a future version of the Chromium package, if I have new hardware, I will again build a package for Slackware 14.1 as well.

Write a comment