My thoughts on Slackware, life and everything

KDE 4.9.5 was released. Next should be 4.10.

When I announced the “final release in the 4.9 series” last month I had no idea that there would be another incremental bugfix release… but the KDE 4.9 Release Schedule page was updated shortly after and here we are with KDE Software Compilation 4.9.5! What happened was that too many bugs had crept in the software right before release of 4.9.4 which were only discovered after the sources had been officially released. You can check out the release notes if you want to read more about this release of KDE 4.9..

And similar to this adding a rather unexpected extension to the 4.9 series, the developers are also talking about adding an extra Release Candidate before giving the green light to KDE SC 4.10. Several proposals for improvements in Dolphin and Akonadi/nepomuk are considered important enough that these patches should be added before releasing 4.10. This seems to be irritating several other distro packager teams who – unlike Slackware – have fixed release dates and therefore, fixed freeze periods. Well, we don’t suffer from a week’s delay and I would say, add those patches and make 4.10 a solid first release!

In spite of that (my opinion is irrelevant in the above story) the recent slips in the KDE release schedule and discovery of too many critical last-moment bugs make me a bit wary about possible resource issues in the KDE developer community. I hope this is not the start of a trend.

Another thing should be mentioned. I don’t know how many people use Kolab groupware in their organization (or at home) but if you do, you will have noticed that support for Kolab has disappeared from Slackware KDE packages after 4.8.x (meaning that Slackware’s own KDE still supports Kolab groupware). I discussed the lack of Kolab support in KDE 4.9 with one of the people using my packages. Indeed KDE 4.9 and later needs a couple of additional packages in order to be able to support the Kolab groupware server like it did in earlier versions. You will need libkolab, libkolabxml and this in turn needs xerces-c to compile. I added SlackBuild scripts and sources for these kolab dependencies in the “deps” directory of the KDE 4.9.5 sources, and xerces-c can be obtained from So: if you need Kolab support, then you have to build packages for these dependencies (first xerces-c, then libkolabxml, then libkolab) and then rebuild the kdepim-runtime package of KDE 4.9.5.

I have no idea if this will ever end up in Slackware proper but it is not hard to add yourself.

Anyway. On with the show.

As you may expect, the Slackware packages for KDE SC 4.9.5 are ready for download and installation. Remember: my ktown packages for KDE are meant to be used on Slackware-current, since that is what they are built on. But the development of -current still has not deviated too much from the latest stable release (14.0), so that these KDE 4.9.5 packages work without any issue on Slackware 14. That is why you will find the packages in a “14.0” directory.

How to upgrade to KDE 4.9.5? Whether you are upgrading from the stock KDE 4.8.5 of Slackware 14.0/current, or if you are upgrading from my previous 4.9.4 packages, you will find all the installation/upgrade instructions that you need in the accompanying README file.

You are strongly advised to read and follow these instructions!

Highlights for the new set of Slackware packages:

  • You will find five updated dependencies compared to Slackware’s own KDE 4.8.5: akonadi, qt, shared-desktop-ontologies, soprano, virtuoso-ose.
  • Some of the “extragear” of the KDE in Slackware 14/current has been updated: with new versions of kdevelop, kdevplatform and oxygen-gtk2.
  • The “extragear” section also introduces two new packages: oxygen-gtk3 (compared to the stable Slackware) which should give any software which uses the GTK+3 widget set a nice integrated look and feel when you run it in KDE; and kio-mtp which is required in order to access and manage files on devices running Android 4.0 and later. I heard that the version which I added to the KDE 4.9.4 set did not work so well, therefore I upgraded to the latest git snapshot. Feedback is welcome.
  • Compared to KDE 4.8.5, there were two package removals:
    • kdemultimedia has been split up into several smaller individual packages.
    • ksecrets has been removed completely in the 4.9.x series.

Download locations (using a mirror is preferred:

Have fun! Eric


  1. weput


    happy new year eric.

  2. Mike Langdon (mlangdn)

    Thanks, Eric! Something to do before bedtime….

  3. escaflown

    Thanks, Eric!

  4. tallship

    Yes let’s hope this is the last before 4.10. I posted a link to this article in the G+ Slackware Linux Community here:

    And thanks for the SBo’s for the Kolab support too AlienBob 🙂

    Kindest regards,



  5. kabamaru

    Eric, thanks for this. This is the first time I built this from source using your SlackBuilds. I noticed a couple of things:

    1. The SlackBuilds don’t have the “$TAG” variable. I used sed to append “alien” but I was wondering why not add the string by default, since it is quite handy when managing packages.

    2. All scripts use $TMP except for deps/updates.SlackBuild which has “/tmp” hardcoded. As a result, if you export a different $TMP, the script will fail to install the dep packages.

  6. alienbob

    Hi kabamaru

    About that “/tmp” that should be fixed indeed, I will change it to $TMP . Thanks.

    The KDE build scripts do not use a $TAG variable because the whole KDE.SLackBuild framework is copied straight into slackware-current from time to time and I want Patrick to have as little work as possible when integrating a new KDE into Slackware.

    What I do after compiling the packages and before uploading them to my mirrorserver, is to run a script which renames all packages (and .txt as well as .asc files) in a certain directory by adding an “alien” tag.
    This is the content of that script:

    # — 8< ----------------------- #!/bin/sh [ -n "$1" -a -d $1 ] && TARGETDIR=$(cd ${1}; pwd) || TARGETDIR=$(pwd) echo "Adding 'alien' tag to files in ${TARGETDIR}..." for FEXT in txz txz.asc txt ; do find ${TARGETDIR} -name "*.$FEXT" | grep -v [0-9]alien | \ while read FILE do mv -i $FILE $(dirname $FILE)/$(basename $FILE .$FEXT)alien.$FEXT done done # --- 8< ----------------------- Eric

  7. kabamaru

    Fair (more than) enough 😉 Thanks again, Eric.

  8. Jeff H

    Thanks Much for the packages!

  9. zobtik

    Hi Eric. I have a question about libkolabxml. It turns out that I’m unable to build it because of missing XSDCXX – “Could NOT find LibkolabxmlDependencies (missing: XSDCXX”). So I went to their site and downloaded it, but it complains about libcult wich in turn complains about something else 🙂 Any hints about what to do? It’s a stock x64 slack machine.
    Best regards,


  10. alienbob

    Hi zobtik

    Now you realize why I hesitated with adding builds for Kolab support. There is a fairly long dependency chain and all these packages would have to be added to Slackware. I have not tried building libkolabxml, I only verified that it would require a lot of extras, so I have no idea what else you might encounter when you are compiling libkolabxml… good luck.


  11. uche

    okular not opening pdf
    invalid plugin factory for okulargenerator_poppler

  12. Geremia


    Check this:
    ldd /usr/lib64/kde4/*okular* | grep -i found

    You might need to install openjpeg.

Leave a Reply

Your email address will not be published. Required fields are marked *

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

© 2024 Alien Pastures

Theme by Anders NorenUp ↑