My thoughts on Slackware, life and everything

Plasma 5 for Slackware – November ktown release

Dear all, today I released KDE-5_19.11 and it comes with some upgrades to official Slackware packages. Don’t worry – Pat Volkerding kindly added the shared libraries of the official Slackware packages to aaa_elflibs, so if you have been updating your Slackware-current installation properly then nothing will break when you update Slackware’s exiv2 and LibRaw packages to the newer versions contained in the November release of ‘ktown‘.
Official Slackware package updates for exiv2 and LibRaw will come sometime soon, but it will require Pat to recompile several other packages as well that depend on exiv2 and/or LibRaw. I needed the new exiv2 to compile the latest digikam, so I was pleased with Pat’s cooperation to make this a smooth ‘ktown‘ upgrade for you.

The packages for KDE-5_19.11 are available for download from my ‘ktown‘ repository. As always, these packages are meant to be installed on a full installation of Slackware-current which has had its KDE4 removed first. These packages will not work on Slackware 14.2.

What’s new in the October 2019 release

This month’s KDE Plasma5 for Slackware contains the KDE Frameworks 5.64.0, Plasma 5.17.2 and Applications 19.08.3. All this on top of Qt 5.13.2.

This month’s updates to the ‘deps’ are: qt5 and PyQt5.
Fresh additions are: LibRaw and exiv2. These are stock Slackware packages and the two are being upgraded ahead of Slackware, so that the Plasma5 packages can pick them up. Pat added the shared libs for the older releases to ‘aaa_elflibs’ so that none of the Slackware packages will break when you install this month’s Plasma5 packages.
And I have removed qt5-speech because I overlooked that this is already part of the big qt5 package.

I rebuilt kdelibs in the KDE4 section, just like Pat did for Slackware. This removes hardcoded TLSv1 allowing TLSv1.1 and TLSv1.2.

Frameworks 5.64.0 is an incremental stability release, see:

Plasma 5.17.2 is a an incremental bug-fix release in the 5.17 cycle of the KDE desktop environment. See

In plasma-extra I updated latte-dock.

Applications 19.08.3 is a stability and bugfix update for the 19.08 cycle, see

In applications-extra I updated digikam, kile (finally 3.0 beta 3!), kstars and kdevelop-pg-qt, kdevelop, kdev-php, kdev-python. Due to the new exiv2 and LibRaw I rebuilt krename and krita.

KDE Telepathy is no longer part of my ‘ktown’ distribution of KDE Plasma5.

Where to get it

Download the KDE-5_19.11 from the usual location at . Check out the README file in the root of the repository for detailed installation or upgrade instructions.

Development of Plasma5 is tracked in git: .
A new Plasma5 Live ISO will arrive later this week (hopefully… I have some stuff high on my TODO list) and you will find it at (rsync://

Have fun! Eric


  1. Regnad Kcin

    Works good. Might be even more speedy and responsive than previous upgrade. ????. (Chinese works too.)

  2. Tom

    Upgraded this morning and it works flawlessly so far. Thanks Eric.

  3. Helios

    Thank you very much. I found that dvdauthor (spumux) needs also to be recompiled (with the new imagemagick).

    • KG Hammarlund

      Might be tricky, dvdauthor seems require an api header that was part of the previous imagemagick package (/usr/include/ImageMagick-6/magick/api.h) but has been removed from imagemagick-7.
      Don’t know (beyond my competence) if this can be solved by some kind of patch.

  4. Lioh

    Smooth as always! Thanks a lot for your work Eric.

  5. Gérard Monpontet

    Works here, (QScintilla-2.11.3-x86_64-1.txz: Upgraded. in current) libburn-1.5.2 work here.

    thanks , Eric 😉

  6. Eduardo

    Thank you Eric! Upgrading right now.
    I also saw that isl got upgraded in -current, I would like to know about whether it works OK with your Plasma before upgrading.
    Will update once the upgrade process is finished.

  7. Eduardo

    Upgraded and so far everything is OK. Thanks again Eric for a fantastic upgrade.

  8. Eduardo

    Hi Eric! Just a question:
    Calligra Stage seems to be missing from your Calligra package. Is this on purpose?


    • alienbob

      Calligra Stage is unmaintained software and is not built by default. You can apparently build it if you add:
      to the cmake invocation but I am not going to do that for my package.

      • Eduardo

        I understand Eric. Thanks for the explanation. I concur with your criterion. Sadly, the official Calligra website does not have any hint of that (not a surprise, really).

  9. Francesco Petronella

    Seems like the upgrade broke my ability to shutdown or reboot from X. I start the server with startx, and if I try to shutdown or reboot using KDE, the screen goes black with only the cursor still on, and stays like that. Slackware current

    • alienbob

      The probable causes for such an issue are usually that you forget to install or upgrade a package,
      You do not give any detail, so all I can tell you that I have multiple computers here which still work fine.

      • Francesco Petronella

        I’m willingly to give any detail request, I just don’t know which (also, thanks for the great work). I tried reinstalling all the packages from ktow. Slackpkg install-new doesn’t give me any missing package, also

        • alienbob

          The command “slackpkg install-new” only works for packages that got added to Slackware itself. It does not work for 3rd party repositories. You do not mention slackpkg+ but if you used that and my repository was called ‘ktown’ in your slackplgplus.conf, then “slackpkg install ktown” would install any package you overlooked.

          • Francesco Petronella

            Sorry, I didn’t mention I already use slackpkg+. Trying slackpkg install ktown_test (is how I named the repository in my conf) doesn’t give me any package missing too. I spotted an error on the console, threw after akonadi shuts down: “ksmserver failed to complete logout”. Tryed to search it on google and all the solutions proposed (deleting /var/tmp/kdecache…, killing the process and rebooting, etc.etc.) with no luck, apparently

  10. tobyl

    Eric, great release as usual…
    My question is not about this specific release, but seems as good a place to ask as any.
    Dolphin says when klicking on Network:
    The KDNSSD library has been built without Zeroconf support.
    I’m currently playing with something that seems to want to use zeroconf (DLNA connnection to audio player on RPi) and I wondered whether there was a reason why this support is not built in?
    many thanks,

    • alienbob

      You’d need avahi to enable zeroconf support. Slackware does not contain that package, and it’s very likely that it will not get added either, so I am not adding it to my ‘ktown’ package set.
      You’ll have to do the rebuilding yourself.

  11. tobyl

    I suspected that would be the reply. So it would be compile & install avahi, then recompile kdnssd I guess.


  12. Owen Greaves

    Just dropping a note – I don’t have an error in the logs – running this desktop no longer works after upgrading to Kernel 5.4.1 -current. I have been running -current for a good long time, but the recent Kernel upgrade seems to be an issue for Plasma 5 / KDE 5

    I am / was able to run all other Desktop environments but Plasma. It would be easy to assume your next release will most likely fix it : )


    • Ricardo

      Hi Owen, no problems here with kernel 5.4.1 and the latest Plasma from ktown. I’m running on an Intel Core i5 with integrated graphics.

      What kind of graphics card do you have?
      Maybe it’s a driver issue.

      • Owen Greaves

        I’m running an HD8400 Radeon / R3 Series – it’s a laptop. I normally just use the default drivers, not proprietary drivers. I see on LQ others are experiencing similar issues.

        • alienbob

          No issue here with slackware64-current, the 5.4.1 kernel and Plasma5. Using Intel GPU.

          • Owen Greaves

            Hey Eric,
            I’m certain it’s something specific to my Laptop – as I it everything running on an older Tower just fine – I’m currently doing a clean 14.2 install, and then upgrade to -current….then I’ll get to Plasma – just going thru all the steps.

  13. alienbob

    Owen, you can do a straight -current installation instead of the laborious process of first installing 14.2 and then upgrading to -current. Downloading my -current ISO uses as much bandwidth as an upgrade from 14.2. Either get the full ISO from or else the mini ISO and then do a HTTP network installation using your fastest Slackware-current mirror.

    Also, did you check /varlog/Xorg.0.log for apparent issues? And if your computer boots into runlevel 4, SDDM will write the user session’s errors into ~/.local/share/sddm/ – perhaps you’ll find something relevant in there.

    • Owen Greaves

      Ya, I actually have your -current .iso, thanks for the tip….having said that, I thought it might be wise to go thru my long way, to see if anything comes up before I install Plasma – the Laptop is somewhat old – 2010 – so I’m curious if I’m having age problems, just my 62 year old body : )

  14. Owen Greaves

    Hi Eric,

    Ok, the install that failed….failed to load libinput – something like that – the reason me thinks is….I used Slackpkg+ and installed ktown rather than using the rsync method (download & install)
    By using your rsync instructions, Plasma now works again. : ) I figured using Slackpkg install ktown would do the same thing, but something gets missed.

    • alienbob

      I guess you were Mobile1 on LQ then…

  15. Steve

    I just tried installing s*64_current+Plasma5 (Nov version) and having some issues with kactivitymanagerd crashing on KDE start. Below is a snippet of the crash report. Maybe QT5 needs updating? Anyone else seeing anything like this? It crashes recursively on starting Plasma. Each time I start any KDE application the kactivitymanagerd crash report pops up. Everything was downloaded fresh in the last couple days from the either with wget, rsync or slackpkg+

    Application: kactivitymanagerd (kactivitymanagerd), signal: Aborted
    Using host libthread_db library “/lib64/”.
    [Current thread is 1 (Thread 0x7fc581fc87c0 (LWP 29350))]

    Thread 6 (Thread 0x7fc57affd700 (LWP 29355)):
    #0 0x00007fc585178a19 in poll () from /lib64/
    #1 0x00007fc58219963e in ?? () from /usr/lib64/
    #2 0x00007fc58219975f in g_main_context_iteration () from /usr/lib64/
    #3 0x00007fc58587339b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/
    #4 0x00007fc58581e92b in QEventLoop::exec(QFlags) () from /usr/lib64/
    #5 0x00007fc585658c81 in QThread::exec() () from /usr/lib64/
    #6 0x000000000040d60a in ?? ()
    #7 0x00007fc585659cc3 in ?? () from /usr/lib64/
    #8 0x00007fc58489319c in start_thread () from /lib64/
    #9 0x00007fc5851844af in clone () from /lib64/

    Thread 5 (Thread 0x7fc57b7fe700 (LWP 29354)):
    #0 0x00007fc582196770 in ?? () from /usr/lib64/
    #1 0x00007fc582198b7b in g_main_context_prepare () from /usr/lib64/
    #2 0x00007fc582199573 in ?? () from /usr/lib64/
    #3 0x00007fc58219975f in g_main_context_iteration () from /usr/lib64/
    #4 0x00007fc58587339b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/
    #5 0x00007fc58581e92b in QEventLoop::exec(QFlags) () from /usr/lib64/
    #6 0x00007fc585658c81 in QThread::exec() () from /usr/lib64/
    #7 0x000000000040d5da in ?? ()
    #8 0x00007fc585659cc3 in ?? () from /usr/lib64/
    #9 0x00007fc58489319c in start_thread () from /lib64/
    #10 0x00007fc5851844af in clone () from /lib64/

    Thread 4 (Thread 0x7fc57bfff700 (LWP 29353)):
    #0 0x00007fc582196805 in ?? () from /usr/lib64/
    #1 0x00007fc582198b7b in g_main_context_prepare () from /usr/lib64/
    #2 0x00007fc582199573 in ?? () from /usr/lib64/
    #3 0x00007fc58219975f in g_main_context_iteration () from /usr/lib64/
    #4 0x00007fc58587339b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/
    #5 0x00007fc58581e92b in QEventLoop::exec(QFlags) () from /usr/lib64/
    #6 0x00007fc585658c81 in QThread::exec() () from /usr/lib64/
    #7 0x000000000040d5aa in ?? ()
    #8 0x00007fc585659cc3 in ?? () from /usr/lib64/
    #9 0x00007fc58489319c in start_thread () from /lib64/
    #10 0x00007fc5851844af in clone () from /lib64/

    Thread 3 (Thread 0x7fc580a86700 (LWP 29352)):
    #0 0x00007ffe67fb09c4 in clock_gettime ()
    #1 0x00007fc585192c86 in clock_gettime () from /lib64/
    #2 0x00007fc585872d91 in ?? () from /usr/lib64/
    #3 0x00007fc585871759 in QTimerInfoList::updateCurrentTime() () from /usr/lib64/
    #4 0x00007fc585871cd5 in QTimerInfoList::timerWait(timespec&) () from /usr/lib64/
    #5 0x00007fc58587312e in ?? () from /usr/lib64/
    #6 0x00007fc582198c2f in g_main_context_prepare () from /usr/lib64/
    #7 0x00007fc582199573 in ?? () from /usr/lib64/
    #8 0x00007fc58219975f in g_main_context_iteration () from /usr/lib64/
    #9 0x00007fc58587339b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/
    #10 0x00007fc58581e92b in QEventLoop::exec(QFlags) () from /usr/lib64/
    #11 0x00007fc585658c81 in QThread::exec() () from /usr/lib64/
    #12 0x00007fc585aaf456 in ?? () from /usr/lib64/
    #13 0x00007fc585659cc3 in ?? () from /usr/lib64/
    #14 0x00007fc58489319c in start_thread () from /lib64/
    #15 0x00007fc5851844af in clone () from /lib64/

    Thread 2 (Thread 0x7fc581293700 (LWP 29351)):
    #0 0x00007fc585178a19 in poll () from /lib64/
    #1 0x00007fc584abed17 in ?? () from /usr/lib64/
    #2 0x00007fc584ac080a in xcb_wait_for_event () from /usr/lib64/
    #3 0x00007fc581eb03c0 in ?? () from /usr/lib64/qt5/plugins/platforms/../../../
    #4 0x00007fc585659cc3 in ?? () from /usr/lib64/
    #5 0x00007fc58489319c in start_thread () from /lib64/
    #6 0x00007fc5851844af in clone () from /lib64/

    Thread 1 (Thread 0x7fc581fc87c0 (LWP 29350)):
    [KCrash Handler]
    #5 0x00007fc5850ae20b in raise () from /lib64/
    #6 0x00007fc585090524 in abort () from /lib64/
    #7 0x00007fc5856229a3 in QMessageLogger::fatal(char const*, …) const () from /usr/lib64/
    #8 0x00007fc5795e7d14 in ?? () from /usr/lib64/qt5/plugins/kactivitymanagerd/1/
    #9 0x00007fc5795e9d6c in ?? () from /usr/lib64/qt5/plugins/kactivitymanagerd/1/
    #10 0x00007fc5795ea274 in ?? () from /usr/lib64/qt5/plugins/kactivitymanagerd/1/
    #11 0x00007fc5795ef666 in ?? () from /usr/lib64/qt5/plugins/kactivitymanagerd/1/
    #12 0x000000000040c442 in ?? ()
    #13 0x000000000040d399 in ?? ()
    #14 0x0000000000409c3d in ?? ()
    #15 0x00007fc58584a192 in QObject::event(QEvent*) () from /usr/lib64/
    #16 0x00007fc585d5fb82 in QGuiApplication::event(QEvent*) () from /usr/lib64/
    #17 0x00007fc5863cdb5c in QApplication::event(QEvent*) () from /usr/lib64/
    #18 0x00007fc5863c65f2 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/
    #19 0x00007fc5863cf6a0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/
    #20 0x00007fc58581fc62 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib64/
    #21 0x00007fc585822768 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/
    #22 0x00007fc585873ce3 in ?? () from /usr/lib64/
    #23 0x00007fc582199483 in g_main_context_dispatch () from /usr/lib64/
    #24 0x00007fc5821996d0 in ?? () from /usr/lib64/
    #25 0x00007fc58219975f in g_main_context_iteration () from /usr/lib64/
    #26 0x00007fc585873381 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib64/
    #27 0x00007fc58581e92b in QEventLoop::exec(QFlags) () from /usr/lib64/
    #28 0x00007fc5858260fe in QCoreApplication::exec() () from /usr/lib64/
    #29 0x0000000000408e86 in ?? ()
    #30 0x00007fc585091b5b in __libc_start_main () from /lib64/
    #31 0x0000000000408f7a in _start ()
    [Inferior 1 (process 29350) detached]

    • alienbob

      Try removing the kactivitymanagerd files from your profile. Log out of Plasma5, then:
      $ rm -rf ~/.local/share/kactivitymanagerd
      and restart Plasma5.

      • Steve

        Thanks Eric, Yes this one of the first things I tried. All is good now that I did a fresh rsync of your ktown X86_64 repository. Seems my first try didn’t get all the packages. I have a nice new shiny Slack64-Current with November release of KDE5. Looks great! One disappointment right off the bat is the KDE Development team has really dumbed down the User Manager application. No more KUser which I really liked – but since we have the KDE4 libs I will try to resurrect that old package. Again many thanks for your great support!

  16. David Brooke

    Running your latest kde/qt on top of current64 from 1st december and I’ve got a problem with the screen unlock, i’ve not traced the kde/qt5 issue yet but when attempting to unlock I get the message to use ck-unlock-session from a root termnal.

    Unfortunately this, for me at least, is reliant on qt4 still being installed which I have removed.
    Adding a symlink from /usr/lib64/qt/bin/qdbus to /usr/lib/qt5/bin/qdbus gets the ck-unlock-session script working again or I could have edited the ck-unlock-session script to explicitely use qt5.

    Any pointer for what I might have broken to upset the kde5 screen unlocking in the first place?

    Otherwise everything looks good, keep up the excellent work.

    • alienbob

      Hi David,
      In the comments section of last month’s Plasma5 post some other people were reporting similar issues with screen unlocking, see and the follow-up remarks.
      I have not seen a resolution to this. It’s also a small fraction of users it seems. Perhaps you should report a KDE bug or confirm the bug report which was opened as part of last month’s conversation.

      • David Brooke

        Thanks for th eprompt reply, I’ll look at that thread and check it is not an install problem before I call it a bug.

        • David Brooke

          And it’s an install problem !?!
          If I’d followed the instructions properly and thoroughly removed old packages and added new ones…

          Having checked everything was correct the screen unlock is functioning as it should.

  17. Carlo

    Thank’s for your work for Slackware. In the last 3 issue i have a problem with konqueror “Running as root without –no-sandbox is not supported” but i work only with root, how i can solve it ?

    • alienbob

      Well, you should not be running any desktop environment as root, basically.

  18. Carlo


  19. acidtripper

    Hi, have recently installed it on top of current. Im facing some issues: When i restart from menu it gets hung and doesn’t restart pc at all. I logged in with init4 and plasma-x11.
    Other issue im facing is icons, i install new packages and it doesn’t get updated till reboot.

  20. Widya Walesa

    Hi Eric,

    I’ve forked your kde SlackBuild and updated to fix build with framworks 5.65, plasma 5.17.4 and applications 19.12.0 in this git repo:

    Some changes:
    – deps: Added libaccounts-{glib,qt5}, signond-qt5, signon-plugin-oauth2, signon-ui-qt5
    – deps: Upgraded mlt to 6.18.0.
    – kde: Moved kaccounts-{integration,providers} from telepathy to kdepim
    – kde: Removed modules/telepathy
    – kde: Added frameworks/kquickcharts
    – kde: Added applications/elisa
    – kde: Added kdepim/kio-gdrive

    I’m now using KDE5 with latest frameworks, plasma and applications.
    Thanks for your SlackBuild script.

    • alienbob

      Hi Widya,

      I really do not like bringing back kaccounts-integration from the dead, along with its dependencies. So it will be good to understand how it benefits you? What will it allow you to do that you can not do without?
      Elisa and kio-gdrive are nice but if Plasma5 is ever going to be accepted into Slackware by Pat, the size of the package collection needs to shrink first, not grow even more.

      • Widya Walesa

        KIO-gdrive is using kaccounts:

        As for slackware inclusion, how about if slackware just provide the core functional desktop. I do it like that on my installation. All packages from frameworks and plasma, then several tool like text/picture editor, document/picture viewer, krdc, k3b, and some system tool. I never installing kde video apps.

        Any other packages like kdepim and several packages from applications (games and optional desktop packages) can be moved to applications-extra and can be released somewhere else or maybe just dropped it and lets user pushed to SBo 😛

        What I mean is, because of the development design of KDE 5, as long as slackware can maintain the KDE frameworks and plasma, any user of KDE can installs any KDE application packages on their own as easy as cmake && make && make install.

        • alienbob

          That makes no sense. If Slackware only offers the core of Plasma without the applications that would give its users an incomplete desktop experience. Plasma5 in Slackware should be more than just a glorified Window Manager. I want it to be a complete Desktop Environment which fulfills all my needs for daily work.

          Anyway, it is highly probable that not all of my ‘ktown’ packages will end up in Slackware eventually. The ones that Pat chooses to skip will end up as add-on packages in my ‘ktown’ repository. That may be stuff like speech support and the packages in ‘applications-extra’.

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 ↑