Plasma 5 for Slackware – KDE 5_17.09

For some time now, no news about Plasma 5 for Slackware appeared on this blog. I just have been too occupied with family life and the demands of my day job.

But the configuration of my new server, the one I bought last month, finally is at a point where I can use it for running virtual machines and compiling packages. And it is fast… compiling LibreOffice in 90 minutes where in the past it would take me 10 times as long. Therefore I was able to create a new release of Plasma 5 packages while at the same time working on new LibreOffice packages.

I have uploaded the September ’17 set of Plasma 5 packages for Slackware 14.2 and -current to the ‘ktown’ repository. KDE 5_17.09 contains: KDE Frameworks 5.38.0, Plasma 5.10.5 and Applications 17.08.1. All based on Qt 5.9.1 for Slackware-current and Qt 5.7.1 for Slackware 14.2.
NOTE: I will no longer be releasing Plasma 5 packages for 32bit Slackware 14.2.

What’s new this time

Well, the good news is that ‘qt5‘ for Slackware-current is now at version 5.9.1. I did not want to risk waiting any longer for the 5.9.2 release which should be imminent but who knows what new bugs that will bring. Several of the other “deps” have been updated as well.
I added MP3 support to ‘kwave‘, and updated ‘digikam‘ and ‘krita‘ to their latest releases. Although… on Slackware 14.2 I had to stick with digikam 5.6.0. The newest digikam requires ‘exiv2‘ version 0.26. I did not want to risk breaking other (non-KDE) programs by adding a binary incompatible ‘exiv2‘ package to my ktown repository.
Other than that, it’s mainly stability and bugfix updates in the KDE software collection.

Installing or upgrading Frameworks 5, Plasma 5 and Applications

As always, the accompanying README file contains full installation & upgrade instructions.

Recommended reading material

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

Where to get the new packages for Plasma 5

Package download locations are listed below (you will find the sources in ./source/5/ and packages in /current/5/ and  /14.2/5/ subdirectories). Only “bear” has the packages for now, the mirrors should follow within 24 hours. If you are interested in the development of KDE 5 for Slackware, you can peek at my git repository too.


A new Plasma5 Live ISO image will follow shortly on in case you want to try it out first (check the timestamp of the ISO on the web page).

Have fun! Eric

77 thoughts on “Plasma 5 for Slackware – KDE 5_17.09

  1. That’s awesome Erik, glad to hear your new box is running marathonic compiling sessions.
    I’ll a try the Slackware live, and of course upgrade my system soon.

  2. Eric, I have just upgraded to your new KDE 5_17.09. All good except for Akonadi not working with MariaDB 10.2.

    As far as I can see from

    you haven’t applied any of the patches suggested by Gerard here:

  3. Thank you very much !

    There are some small problems :

    /usr/bin/kile : => not found

    /usr/lib64/qt5/plugins/ => not found

  4. Pingback: Links 12/9/2017: Linux 4.13.1, digiKam 5.7.0 | Techrights

  5. Helios yes I think I will have to recompile kile to let it pick up the new poppler library. About the openconnect library: the README informs you that you have to install the openconnect package separately, it is not part of the ‘ktown’ repository.

  6. Eric, akonadi-17.08.1-x86_64-2alien.txz worked like a charm! Thanks a lot, again!

    As a side note, slackpkg complained about your ktown GPG key:

    ‘/media/nas/mirrors/alienbob/ktown/latest/CHECKSUMS.md5.asc’ -> ‘/dev/shm/slackpkg.eCmJCi/CHECKSUMS.md5-ktown.asc’

    ERROR: Verification of the gpg signature on CHECKSUMS.md5
    failed! This could mean that the file is out of date
    or has been tampered with.

    This has happened only after this most recent update (akonadi and kile). It was clean on yesterday’s update.

  7. I have had a problem on the two machines I am running -current and ktown (one laptop, one desktop, both with intel GPUs) whereby if I suspend the display or change to one of the console TTYs while in a logged in session, the screen doesn’t wake up. And the only way to restore is to kill the X session and restart it.
    It doesn’t happen before login (sddm login screen).
    I cannot find anything in the logs I know of but I may not be looking in the right place.
    Any pointer would be helpful.

  8. I have an Intel GPU in this laptop I am typing on (Lenovo 460): an “Intel Corporation HD Graphics 520 (rev 07)” using the i915 kernel driver. I have never experienced this issue you are describing. I can switch to a console from within this Plasma5 desktop session using Alt-Ctrl-F1 and then switch back later to the X session using Ctrl-F7 without any problem.

  9. Dear eric, i have a small problem. after update kde plasma, then i try to take screenshot in rectangular region with spectacle the shortcut key won\’t launch. the shortcut key still default, has been not changed. Thanks

  10. I have uploaded a new ‘kglobalaccel’ package which fixes the bug Arief mentioned. I also refreshed the ‘akonadi’ package by applying the official patch to make it work with the new mariadb.

    Also note that as of now, the packages in the “ktown” repository are signed with my new GPG key “769EE011” –

    Users of slackpkg+ may want to run the command “slackpkg update gpg” to obtain the new gpg key.

  11. I ran \”slackpkg update\” and \”slackpkg upgrade-all\” today, and it downgraded many KDE apps from 17.08.1 to 4.14.3. Why would this be? My slackpkgplus.conf has this:

    PKGS_PRIORITY=( multilib:.* ktown:.* restricted_current:.* alienbob_current:.* slackpkgplus:.* ponce:.* )

    Is this not configured correctly?

  12. Geremia you seem to be missing the REPOPLUS definition which tells slackpkg which 3rd party repositories to use. Without the REPOPLUS variable, no 3rd party repository will be used at all.
    From /etc/slackpkg/slackpkgplus.conf:

    # List repositories you want to use (defined below)
    # remember to launch ‘slackpkg update’ if you modify that row.
    #REPOPLUS=( slackpkgplus restricted alienbob slacky )
    #REPOPLUS=( slackpkgplus )

  13. Hi Eric,
    thank you for openconnect support!
    Could you please rebuild plasma5-nm against openconnect for Slackware 14.2 also?

  14. Since update to this KDE in Slackware 14.2, no longer see hibernation/suspend option in kickstart menu.
    Anyone else experienced this problem?
    No idea where to dig so far..

  15. Eric, looks like your keys are somewhat invalid to slackpkg+. After run ‘slackpkg update gpg’ with no errors, ‘slackpkg update’ complains with:

    ERROR: Verification of the gpg signature on CHECKSUMS.md5
    failed! This could mean that the file is out of date
    or has been tampered with.

    The keys I have for your repos are:

    ‘/mirrors/alienbob/ktown/latest/GPG-KEY’ -> ‘/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-ktown’
    pub 4096R/769EE011 2016-08-21 Eric Hameleers (Alien BOB)

    URL: [17332/17332] -> “/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-restricted” [1]
    pub 1024D/A75CBDA0 2003-01-17 Eric Hameleers

    ‘/mirrors/alienbob/multilib/GPG-KEY’ -> ‘/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-multilib’
    pub 1024D/A75CBDA0 2003-01-17 Eric Hameleers (IBM Linux)

    URL: [17332/17332] -> “/dev/shm/slackpkg.lpzcMF/gpgkey-tmp-alienbob” [1]
    pub 1024D/A75CBDA0 2003-01-17 Eric Hameleers

    Maybe you’ve forgot to update CHECKSUMS.md5?

  16. Just sorted out problem with hibernation/suspend option.
    Turned out it was due absent upowerd dependencies which gone for some mystical reason..

  17. Deny, what repository causes that error “Verification of the gpg signature on CHECKSUMS.md5 failed”? I did not see that error when I ran an update yesterday evening.

  18. Eric, unfortunately slackpkg+ does not provide a clear indication on which repository triggers a checksum error (maybe there’s room for improvements).

    Anyway, I just ran it again and there was no error. Whichever was the culprit, it’s now fixed.

  19. Just for info Eric, i have ‘pcre2’ and ‘pcre’ installed here:
    and by default ‘qt5’ prefer pcre2 for build, if this two version are installed

  20. Hi, thank you for the update.

    I installed this update on current however the login is very slow, the desktop takes like 3 minutes to show the background image, I checked with htop and iotop but there is no system overloading (cpu is like 10%). I tried to check the .xsession-errors file but kde5 is not creating it.

    Do you know how can I debug the loading?

    Thank you!

  21. Slackware-current’s hplip-3.17.9-x86_64-1 isn’t compatible with Alien’s PyQt and sip packages:

    hp-systray[2185]: error: No module named ‘PyQt4.QtCore’
    hp-systray[2185]: error: Unable to load Qt4/Qt5 support. Is it installed?

    Installing Slackware-current’s latest PyQt and sip packages corrects it.

  22. Obsolete deps packages with current now:

    sni-qt (hplip applet work without this, now)
    poppler need update to 0.59.0

    plasma5, packages need rebuild:
    okular need rebuild with poppler-0.59.0
    kfilemetada5, also

  23. I have uploaded a couple of updated packages

    current/deps/ sip, PyQt, ninja: removed from the ktown -current repository
    because the stock Slackware packages can again be used.
    current/deps/ phonon-vlc: rebuilt.
    current/deps/ poppler: updated (added python3 support).
    current/kde/applications/ kig, okular: rebuilt.
    current/kde/applications-extra/ calligra, kdevelop, kile: rebuilt
    current/kde/applications-extra/ krita: updated.
    current/kde/frameworks/kfilemetadata5: rebuilt.
    current/kde/kde4/ qtruby, smokeqt: rebuilt.
    current/kde/plasma-extra/kdeconnect-framework: updated.
    current/kde/plasma/plasma5-nm: rebuilt.

  24. HI, Eric, i have tested, a new cmake option on my buildscript for two personnal package here:(partitionmanager and digikam)

    this option is:

    this option work perfectly here for this two package,

    and this option make obsolet this line in the buildscrip,
    mkdir -p $PKG/usr/doc/$NAME-$VERSION
    because it’s create before.

    I will try on other packages, to see 😉

  25. Hi Eric,

    Great build!!

    But i do have a question: is Dolphin is being compiled without baloo-widgets, or even baloo itself?
    See this screenshot from current ktown dolphin:
    Now, compare with this screenshot from current KDE Neon:

    There is a lot of information missing from the places and information panel on Dolphin in the current build. Taking a peek at the executable, i saw this:
    slack@CapEnt:/var/log/packages# ldd /usr/bin/dolphin | grep -i baloo

    While on Neon, i have that:

    Is that on purpose? I know that a lot of people hates the metadata framework and the desktop search features of Baloo integrated on Dolphin.


  26. CapEnt indeed, my dolphin gets built after baloo5-widgets and the cmake does complain about not finding it. It’s likely the reason for the difference you are seeing.
    I have updated the build order so that next time dolphin will be built after baloo5-widgets. Let’s see what that does for its search capability.
    Thanks for notifying me about this discrepancy!

  27. Hi Eric,
    since your last upgrade, plasma is literally eating up my laptop! In less than one hour, plasmashell process grows till more than 10G of ram usage (laptop have 15G) !!! How is it possible?
    Please help me, my laptop is unusable!
    thx a lot


  28. Mario please debug your issue if you can and tell me where the root cause is. It’s not my computer so I can not tell you what to do.

    Also, what do you call “last upgrade”? The 5_17.09 release on Sep 11 or the rebuilt packages on Sep 27?

  29. Eric,
    my last upgrde was last sunday, so I’ve the rebuilded packages installed. The I didn’t install the ones of Sep 11.
    Can you provide me some methods to debug plasmashell process?
    Thanks a lot!

  30. Ok… maybe I found the problem… I removed all plasmoids on the desktop (cpu monitor, clock and a launcher), restarted plasmashell and now the memory usage seems to be stable. I’ll keep you update…
    thanks a lot!

  31. Finally I got it… the problem appears for sure when I try to switch between activities. Here the debug of plasmashell:

    SwitcherBackend: FAILED to get the thumbnail “Codice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a” (“Errore non documentato”, “Errore non documentatoCodice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a”, “Dettagli della richiesta:URL: (sconosciuto)Data e ora: martedì 3 ottobre 2017 11:12:09 CESTInformazioni aggiuntive: “)
    SwitcherBackend: FAILED to get the thumbnail “Codice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a” (“Errore non documentato”, “Errore non documentatoCodice di errore sconosciuto: 0\n\nPer piacere, invia una segnalazione dettagliata di bug a”, “Dettagli della richiesta:URL: (sconosciuto)Data e ora: martedì 3 ottobre 2017 11:12:09 CESTInformazioni aggiuntive: “)
    file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
    file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
    file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:365: TypeError: Cannot read property ‘padding’ of null
    file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:364: TypeError: Cannot read property ‘padding’ of null
    file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:363: TypeError: Cannot read property ‘padding’ of null
    file:///usr/lib64/qt5/qml/QtQuick/Controls/ScrollView.qml:362: TypeError: Cannot read property ‘padding’ of null
    file:///usr/lib64/qt5/qml/QtQuick/Controls/Button.qml:99: TypeError: Cannot read property of null
    file:///usr/share/plasma/plasmoids/org.kde.plasma.battery/contents/ui/CompactRepresentation.qml:54:39: Unable to assign [undefined] to int

    The part in italian is the content of the bug request. After this, RAM consumption grows fast and infinitely. I don’t know if there are other behaviours like this. May I’m missing some packages?

  32. The RAM consumption grows also when there is a slideshow as desktop background… in less the 3 minutes, ram consumption grows of 1 GB, with lot of lines like this in debug:
    No metadata file in the package, expected it at: “/path/to/images/folder”

  33. Mario, with a simple “slackpkg upgrade ktown” you are not doing enough. That command will not install any of the packages I add to the repository, it only upgrades packages you already have installed.
    And in this case, “slackpkg upgrade ktown” should be followed by “”slackpkg upgrade-all” to replace my deleted sip, PyQt and ninja packages with the originals from slackware-current.

    Try the command “slackpkg install ktown” and see if that shows any new packages you still have to install.

    And please file a bug on the KDE bugtracker if you can reproduce the memory leak.

  34. First of all, a big thanks to Eric for his untiring efforts in support of Slackware and KDE5 in particular!

    I’m having a problem that has me stumped, and I’m hoping someone has an answer. I have two machines running Slackware-current and Eric’s KDE5, all up to date and running well – except in one respect, namely kdenlive!

    My old desktop machine (now relegated to my workshop) has an AMD Bulldozer processor, 8GB of RAM and an AMD/ATI Gfx card using the kernel (open source) drivers and vdpau.

    The new machine has an Intel I7 quad core, 16GB of RAM and uses Intel graphics and va-api.

    Kdenlive works fine on the old machine. On the new one it crashes all the time, with the most frequent error being:

    KCrash: crashing… crashRecursionCounter = 2
    KCrash: Application Name = kdenlive path = /usr/bin pid = 3479
    KCrash: Arguments: /usr/bin/kdenlive
    *** Error in `kdenlive’: malloc(): memory corruption: 0x00007f0474419180 ***

    All other applications work fine. As far as I can tell, the only major difference between the machines is the AMD vs Intel graphics.

    Does anyone have any ideas what might be causing this, or any other bug-hunting ideas?

    Many thanks!


  35. Myk267 – indeed that bit of text needs to be removed. The commands that follow that remark used to end in a dot. That was not too obvious to some, so I modified the commands to end with a (sub-) directoryname instead.
    I’ll update the README for the next package release, thanks for reporting.

  36. Gérard since I will probably be building Plasma5 packages for some more months (at some point I assume that Patrick will take over) I do want to update the qt5 package to 5.9.2. I am not certain when that will happen – last half of october I will probably be too busy to work on Slackware.

  37. Thanks for all your work.

    I’ve updated kde5 to 17.09, but since 17.07 I noticed that Firefox freezes some seconds at startup before becoming usable.

    Also – but maybe it’s not related to kde5 since I’m not using it often- hp-toolbox offers a beautiful segfault. It seems related to python-2.7. Here’s gdb back trace (last lines)
    (gdb) backtrace
    #0 0x00007ffff6d52ff6 in strlen () at /lib64/
    #1 0x00007ffff7a6b657 in PyString_FromFormatV () at /usr/lib64/
    #2 0x00007ffff7ad6c0f in PyErr_Format () at /usr/lib64/
    #3 0x00007fffe9ea51c7 in () at /usr/lib64/python2.7/site-packages/
    #4 0x00007fffee576826 in initQtGui () at /usr/lib64/python2.7/site-packages/PyQt4/

  38. Alien,
    You can ignore what I said about Firefox : it’s more an extension issue (maybe noscript or requestpolicy) issue. Firefox runs fine without all theses extensions activated.

  39. In dep, json-glib-1.4.2 can be updated (need meson and ninja for build now, no problem here)

    xapian-core-1.4.4 can be updated (no problem here)

    new other:


    Also new version of krita, sddm, kpmcore, partitionmanager, are available.

    just build plasma-5.11.0 with qt5-5.9.2, compil and work fine 😉

  40. Thanks very much for your work. Pretty much everything is working well here, except for the aforementioned bug with System Settings (thanks for the workaround). Plasma 5 is really nice to use.

    There is one bug that has been around for a long time with Plasma 5, which causes down-sampled images to appear blurry when used as a background:

    The latest on the bug tracker indicates that it is an upstream Qt bug, fixed in 5.9.1. I see you already have that version in your packages for current, but a rebuild for 14.2 would be nice in the future.

    Thanks again!

  41. Hi montagdude – I will probably never upgrade my qt5 package for Slackware 14.2, instead I keep it in sync with the version on If that moves up to 5.9 then so will my version of the package.

Leave a Reply to Mario Cancel 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.