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

My Favourites



July 2016
« Jun    

RSS Alien's Slackware packages

RSS Alien's unofficial KDE Slackware packages

RSS Alien's multilib packages

RSS Slackware64-current


July ’16 security fixes for Java 8

icedteaOn the heels of Oracle’s July 2016 security updates for Java 8, the icedtea folks have released version 3.1.0 of their build framework so that I could create packages for OpenJDK 8u101_b13 or “Java 8 Update 101 Build 13”  (and the JRE too of course).

Here is the list of security fixes and CVE‘s as taken from the announcement on Andrew Hughes’s blog:

Download locations:

If your applications are not yet ready for Java 8, I still maintain the Java 7 packages under new names:”openjdk7″ and “openjre7”. Note that my Java 7 and Java 8 packages (e.g. openjdk7 and openjdk) can not co-exist on your computer because they use the same installation directory.

There is no more need for a separate “rhino” package (implementation of the JavaScript engine used by OpenJDK) because in OpenJDK 8, this functionality is provided natively using the internal “nashorn” library.

Note about usage:

Remember that I release packages for the JRE (runtime environment) and the JDK (development kit) simultaneously, but you only need to install one of the two. The JRE is sufficient if you only want to run Java programs (including Java web plugins). Only in case where you’d want to develop Java programs and need a Java compiler, you are in need of the JDK package.

Optionally: If you want to use Java in a web browser then you’ll have to install my icedtea-web package too. While Oracle’s JDK contains a browser plugin, that one is closed-source and therefore Icedtea offers an open source variant which does a decent job. Note that icedtea-web is a NPAPI plugin – this prevents use of Java in Chrome & Chromium because those browsers only support PPAPI plugins, but you’ll be OK with all Mozilla [-compatible] browsers of course.

Have fun! Eric

KDE 5_16.07 for Slackware 14.2 and -current

plasma5_startupI released a Slackware Live ISO containing Plasma 5.7.0 a few weeks ago, but did not make a fuss out of it – in other words, I did not write any communication about it on this blog. The Live ISO was made upon request of the KDE developers who wanted to show off the new Plasma 5.7 on Live Editions of as many distro’s as possible.

And now that all major KDE components have had new releases, it is time to package them up and create my habitual “KDE of the month release” for Slackware along with a proper announcement.

KDE 5_16.07 is the July release of the combined KDE Frameworks 5.24.0, Plasma 5.7.2 and Applications 16.04.3 for Slackware, built on top of Qt 5.6.1. You can enjoy the latest KDE 5 on Slackware 14.2 and -current.



As promised, I have used the release of Slackware 14.2 to re-arrange stuff in the ‘ktown’ repository. I consider Plasma 5 to be a stable and enjoyable desktop experience, so the packages have moved from “testing” to “latest” for both Slackware 14.2 and slackware-current (there is no difference between the two at the moment, I built the packages on Slackware 14.2 but they are usable on -current as well). The Plasma5 repository on still has a “current/testing” section but with the use of symlinks, it is pointing to the “14.2/latest” package set which is where you will get your stable releases in future.

If you use a package manager that supports 3rd party repositories (slackpkg+, slapt-get) you may want to change the string “testing” to “latest” in the ‘ktown’ repository URL!

I may wait until Pat adopts Plasma 5 into slackware-current but if that takes too long, I may just start diverging the two repositories because I want to investigate Wayland support in Plasma 5. This means, dear reader, if you want a pleasant and stable Plasma 5, stick with the “14.2/latest” and “current/latest” URLs. And if you want to be surprised some day, track the “testing” repository instead, where things may break without warning. You have been warned 🙂

What’s new in KDE 5_16.07?

  • Frameworks 5.24.0 is an enhancement release with no new frameworks this time. See
  • Plasma 5.7.2 is an incremental bugfix release of the 5.7 series. See . The Plasma 5.7 series has some long-anticipated highlights that improve the user experience: “agenda view” is back in the calendar, and the volume control applet is way more functional, amongst others.
  • Applications 16.04.3 is also a maintenance release. See . Nothing exciting to report.
  • After the updates of Qt5 and Qt5-webkit packages in the “deps” directory last month, several other “deps” packages were still in need of an update or rebuild so I took care of that. The rebuilt/upgraded packages are: ‘sni-qt’, ‘qca-qt5’, ‘PyQt5’, ‘polkit-qt5-1’, ‘phonon’, ‘grantlee’ and ‘qt-gstreamer’. The ‘sip‘ package has been removed from “deps” because Slackware 14.2 now has a proper version of that.
  • There’s a new KF5 port of ‘skanlite’ in the “kde/applications-extra” directory along with the previously added KF5 port of ‘ktorrent’.  And ‘kjots’, previously contained in KDE PIM, has been separated into its own package in the “kde/applications” directory.
  • The ‘noto-font-ttf‘ package was rebuilt because the VERSION number contained dashes, which created an illegal package name. You will have to remove the old package manually with “removepkg /var/log/packages/noto-font-ttf-2015-09-29-noarch-1alien“.

This upgrade should be straightforward if you already have Plasma 5 installed. See below for install/upgrade instructions. And if you want to check it out before installing, I will be generating new Live ISO’s soon: for all variants, PLASMA5 included. They will become available at soon. Check the timestamp of the “slackware64-live-plasma5-current.iso” ISO.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

You can skip the remainder of the article if you already have my Plasma 5 installed and are familiar with the upgrade process. Otherwise, stay with me and read the rest.

As always, the accompanying README file contains full installation & upgrade instructions. Note that the packages are available in several subdirectories below “kde”, instead of directly in “kde”. This makes it easier for me to do partial updates of packages. The subdirectories are “kde4“, “kde4-extragear“, “frameworks“, “kdepim“, “plasma“, “plasma-extra“, “applications“, “applications-extra” and “telepathy“.

Upgrading to this KDE 5 is not difficult, especially if you already are running KDE 5_16.06. You will have to remove old KDE 4 packages manually. If you do not have KDE 4 installed at all, you will have to install some of Slackware’s own KDE 4 packages manually.

What I usually do is: download all the ‘ktown’ packages for the new release to a local disk. Then run “upgrade –install-new” on all these packages. Then I check the status of my Slackware-current, upgrading the stock packages where needed. The slackpkg tool is invaluable during this process of syncing the package installation status to the releases.


If you are using slackpkg+, have already moved to KDE 5_16.06 and are adventurous, you can try upgrading using the following set of commands. This should “mostly” work but you still need to check the package lists displayed by slackpkg to verify that you are upgrading all the right packages. Feel free to send me improved instructions if needed. In below example I am assuming that you tagged my KDE 5 repository with the name “ktown” in the configuration file “/etc/slackpkg/slackpkgplus.conf“):
# slackpkg update
# slackpkg install ktown (to get the newly added packages from my repo)
# slackpkg install-new (to get the new official Slackware packages that were part of my deps previously)
# slackpkg upgrade ktown (upgrade all existing packages to their latest versions)
# slackpkg upgrade-all (upgrade the remaining dependencies that were part of my repo previously)

And doublecheck that you have not inadvertently blacklisted my packages in “/etc/slackpkg/blacklist“! Check for the existence of a line in that blacklist file that looks like “[0-9]+alien” and remove it if you find it!

Recommended reading material

There have been several posts now about KDE 5 for Slackware-current. All of them contain useful information, tips and gotchas that I do not want to repeat here, but if you want to read them, here they are:

A note on Frameworks

The KDE Frameworks are extensions on top of Qt 5.x and their usability is not limited to the KDE Software Collection. There are other projects such as LXQT which rely (in part) on the KDE Frameworks, and if you are looking for a proper Frameworks repository which is compatible with Slackware package managers such as slackpkg+, then you can use these URL’s to assure yourself of the latest Frameworks packages for Slackware-current (indeed, this is a sub-tree of my KDE 5 repository):

Where to get the new packages for Plasma 5

Download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ subdirectories). If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.

Using a mirror is preferred because you get more bandwidth from a mirror and it’s friendlier to the owners of the master server!

Have fun! Eric

July ’16 security fixes for Adobe Flash

adobe_flash_8s600x600_2Due to a holiday stay in Brittany (France) last week, the monthly updates for Adobe’s Flash player plugins took a little longer to reach my Slackware repository. Read the Flash player  security update of July 12th if you want to know more about all the CVE entries the update is addressing.

Good news by the way: it is no longer required to extract the PepperFlash library from a Google Chrome RPM. Adobe hosts the PPAPI plugins on their own web server now. This has another (positive) consequence: there is a 32bit pepperflash plugin again!

The updated plugin for the Chromium browser (chromium-pepperflash-plugin) has the version number while the plugin for Mozilla browsers (flashplayer-plugin) is now at version

Slackware packages for these Flash plugins are available for download & install in the following locations:

If you are using the slackpkg+ extension for slackpkg, then you just run “slackpkg update && slackpkg upgrade flash”. Alternatively, you can subscribe to my repository RSS feed to stay informed of any updates.


LibreOffice 5.1.4 (bugfix release)

libreoffce_logoThe Document Foundation released Libreoffice 5.1.4 on June 23, but I was kept busy with preparing my own packaging and scripting stuff for the release of Slackware 14.2. In addition, a new release of Plasma (5.7) is near, for which I promised a Live ISO to be available on July 5.
Still, I thought new packages were needed after someone pointed out that there is a CVE associated with the 5.1.4 release because it fixes a security bug:  CVE-2016-4324. Therefore I am pleased to announce the immediate availability of Slackware (14.2 and -current) packages for LibreOffice 5.1.4.
According to the announcement this LO release is “targeted at individual users and enterprise deployments. Users of previous LibreOffice releases should start planning the update to the new version“.



LibreOffice 5.1.4 is otherwise a minor update, focusing on bug fixes.

Packages can be obtained from these mirror sites and probably others too:

Cheers! Eric

PS: for those who had not noticed: the LibreOffice browser plugin (NPAPI based) has been removed in 4.4.0:

Bear is working for its money


This is the bandwidth graph of the last 24 hours for my “bear” server, which I could rent thanks to donations made after the old “taper” server kept buckling under the load of serving Slackware Live ISO images.

Since I made the new Slackware 14.2 data available 24 hours ago, the server has been pushing out 1.67 Terabytes of data, at an average of 155 MBytes/sec. Needless to say that this server was a good investment, I could never have managed this on my old platform.
Thanks for the public interest and have a lot of fun with your shiny new Slackware 14.2 ISO (Live edition or regular installer)!