My thoughts on Slackware, life and everything

KDE 5_16.11 available for Slackware 14.2 and -current

plasma5_startupBack after a hiatus due to my changing employment status: KDE 5_16.11 is my November release of the combined KDE Frameworks 5.27.0, Plasma 5.8.3 and Applications 16.08.2 for Slackware, built on top of Qt 5.7.0. You can use the latest KDE 5 on Slackware 14.2 and -current.

My intention is to keep releasing versions of the stable Plasma 5 software through the “14.2/latest” and “current/latest” URLs. I still carry a “testing” repository but that does not get updated nearly as often and is currently outdated. So please disregard that “testing” area until further notice and be sure to check your automated package management programs for the correct repository URL.

What’s new in KDE 5_16.11?

  • Frameworks 5.27.0 is an enhancement release with no new frameworks this time. See
  • Plasma 5.8.3 is an incremental bug fix release for the 5.8 series. Note that this is the first Plasma 5.8 that goes into my ‘ktown’ packages as you will notice straight away when starting a Plasma session. There is a new ‘loading’ animation again.
    Plasma 5.8 is labeled a Long Term Support (LTS) release. In part this has been done because the developers think that 5.8 marks the point where users who loved KDE 4 and turned away from Plasma 5 should re-evaluate this desktop environment and hopefully want to stay.
    The 5.8 LTS release should work with Qt 5.6.1 but I think it is better to stick with the Qt 5.7 which I already used for the previous ‘ktown’ iteration.
    See and if you want to know more about the LTS, go read:
  • Applications 16.08.2 is a maintenance upgrade. See .
  • Upgrades for kdeconnect and sddm can be found in the ‘plasma-extra’ subdirectory, while a newer skanlite can be found in ‘applications-extra’.

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 a new Live ISO’s soon for the PLASMA5 variant. Look for that ISO on 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.08. 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.08 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):

The same goes for Frameworks for Slackware 14.2 (change ‘current’ to ‘14.2’ in the above URLs).

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


  1. Serega


  2. Eduardo

    Thank you Eric! I just upgraded and it works great so far.

  3. Owen Greaves

    Yep, no issue so far, works great…thanks.

  4. Ricardo J. Barberis

    Thanks Eric!

    Two quick questions out of curiosity:

    1- I thought that on 14.2 you planned to stick with Qt 5.6, as that is also an LTS release but you upgraded to 5.7. Any particular reason for that?

    2- I was about to ask about your work situation but went and finished reading your original post. So glad to hear about your job offer from ASML! Am I correct to think you finally got that job?


  5. Guest


    I had 5_16.08 installed and was feeling adventurous enough to update using slackpkg+.

    Everything is working but i skiped the last slackpkg command:

    # slackpkg update (Ok)
    # slackpkg install ktown (OpenAL was the only package i selected, ignored language packages)
    # slackpkg install-new (Nothing showed up)
    # slackpkg upgrade ktown (Ok)
    # slackpkg upgrade-all (What this does is downgrade all upgraded packages from previous step to its previous versions?)
    slackpkg upgrade akonadi:
    Package akonadi-16.08.2-x86_64-1alien upgraded with new package ./akonadi-1.13.0-x86_64-3.txz
    Then Akonadi doesn’t even open anymore

    slackpkg upgrade ktown:
    Package akonadi-1.13.0-x86_64-3 upgraded with new package ./akonadi-16.08.2-x86_64-1alien.txz.
    Then akonadi works again.

    My slackpkgplus conf:
    REPOPLUS=( ktown )

  6. Guest

    I run slackware in a old machine and i noticed that “fc-cache” took 90% of cpu for about 1 minute everytime i log-in on KDE.

    Maybe because i have a lot of font files in my home folder, not sure. I found it inside rc.d/rc.M and disabled it. So far stuff still working, if it’s wrong please someone let me know.

  7. alienbob

    Hi “Guest”

    You did not configure your slackpkgplus.conf file correctly if you did not specify PKGS_PRIORITY.
    Read the sample configuration file. It contains these lines:

    # if you want to install ‘ktown’ repository you must set it here
    #PKGS_PRIORITY=( ktown )
    # and DO NOT MISS to read special instruction
    # on /usr/doc/slackpkg+-*/repositories.txt

  8. Arief JR

    thank you eric, it\’s cool.

    Hi Guest, if do not want high a resource so put this fc-cache into cron job without disable rc.d/rc.M and fc-cache in rc.M line remove.
    In here it\’s working,

  9. LoneStar

    just one thing: YAY!

  10. Gérard Monpontet

    Work here, Eric, just a comment, baloo (4) and baloo-widgets (4) are obsolet now, just need recompile kde-baseapps and kget, tested here with kde applications 16.08.2 and the new applications 16.08.3.
    all compile perfectly without baloo, and baloo-widget 😉

  11. bam

    Can’t add Telegram in Online Accounts:
    “This IM Account cannot be created – a Telepathy Connection Manager named ‘morse’ is missing or it cannot handle protocol ‘telegram’. Please try installing morse with your package manager.”

    Also, pressing “Google” button just makes nothing

  12. kjhambrick

    Eric —

    I was going to run `upgradepkg calibre-2.71.0-i486-1alien.txz` on my Slackware64 14.2 + Multilib LapTop.

    I am running standard Slackware64 14.2 KDE Version 4.14
    on QT version 4.8.7.

    I’ve already got calibre-2.61.0-x86_64-1alien installed.

    It runs great ! Thanks very much !

    Before running upgradepkg, I was looking at dependencies for the calibre update.

    I’ve got all the dependencies installed, but I do see that qt5 version 5.7.0 is available.

    And another dependency is qt5-webkit …

    My question is: Is the currently available qt5-webkit version 5.6.1 compatible with qt5 version 5.7.0 ?


    — kjh

  13. alienbob

    bam – I have not added telepathy-morse to my package set, hence the error when trying to configure a Telegram account.
    About Google accounts in KDE Telepathy, I have never been able to use one. Always getting an authentication error. No idea if that is (partially) caused by me using two-factor authentication on Google.

  14. alienbob

    kjhambrick – I do not understand why you want to upgrade to a 32bit calibre package on a 64bit OS? Bad idea.

    But your question about qt5-webkit is valid. I will upgrade the qt5-webkit package in my slackbuilds repository to 5.7.0 to match it with the qt5 version.

  15. kjhambrick

    Eric —

    oops. cut-n-paste error … I pasted the i486 entry from FILENAMES.TXT instead of the x86_64 entry ( I am running calibre x86_64 ).

    Will wait for the qt5-webkit update then.

    Also saw your post on LQ that qt5 now requires libinput …

    Will install libinput as well.

    Thanks Eric !

    — kjh

  16. alienbob

    I uploaded a new qt5-webkit 5.7.0. And the full list of dependencies for my qt5 package is: libinput, libxkbcommon. The qt5-webkit in turn depends on qt5 and its dependencies.

  17. bam

    Eric, is there any reason you don’t include telepathy-morse? Could you include it in the future? I would try it instead official Telegram app

  18. kjhambrick

    Thank you Eric !

    Installed libinput

    Upgraded qt5, qt5-webkit and calibre.

    Calibre 2.7.1 is working very well over Qt5 5.7.0 on Slackware64 14.2 !

    — kjh

    p.s. sorry if this is the wrong thread for my Calibre Qs and Cs. It seemed like the closest Blog Post since Calibre rides on qt5.

  19. kjhambrick

    oops. that’s Calibre 2.71.0 …

  20. alves

    Don’t work here.

    I have a beautiful black screen, and my /etc/X11/xinit/xinitrc is point to -> xinitrc.plasma

  21. alienbob

    alves – too little information.

  22. Marcus

    After instalation plasma 5.8.3 suspend/reboot/shutdown/logout dont work from KDE. Ksmserver crash with something like “Executable: ksmserver-logout-greeter PID: 6135 Signal: Segmentation fault (11)” Do You have any advice?

  23. Marcus

    It looks like a bug in nvidia driver 375.10(beta). With previous release 370.28 works fine.

  24. Henry Case

    Just so the info is here, (and cause I was notified of a duplicate bug report) if the package kdeconnect-kde from Slackware base repo is installed Dolphin will crash when right-clicking files

  25. MeH

    Dear Eric,

    Thank you for your nice Plasma 5 packages. Although I have set “export LANG=en_US.UTF-8” in my /etc/profile.d/, non-English characters are show like آزÙ?Ù?Ù? دکترÛ?. Is this a Plasma 5 packages bug (It is not the case when I don’t install your Plasma 5 packages)?

  26. alienbob


    The README file for any of my Plasma 5 (ktown) releases contains this:

    If you have Slackware 14.2 or -current’s default KDE 4.14.3 installed:

    # removepkg kdeconnect-kde

    The Pasma 5 packages contain “kdeconnect-framework” which is the version built against KDE Frameworks 5.
    I.e. not a bug.

  27. alienbob

    MeH, that is too little information, so I can not give you an answer.

  28. MeH

    I managed to solve the problem by setting Region to “No Change” in “Settings > Regional Settings > Formats” 😉

  29. alienbob

    Good. The “no change” is the default setting, so what did you have configured previously and why was that necessary?

  30. MeH

    It was set “no change” by default. Trying to solve the problem, I changed it to “United States” which didn’t help. Therefore, I set it again to “no change” and unexpectedly non-Latin characters was shown correctly! It sounds that plasma 5 needed to be noticed to pick up the default value for $LANG when it is not set within plasma 5 itself.

  31. alienbob

    MeH, thanks for explaining that. To me it sounds like a bug, though.

  32. Rudson Alves

    Now it works! My copy of KDE5 had old files. After adding \”–delete\” option in rsync command, this removed the old files and the Plasma 5 installation worked fine.

    Thanks Eric, great job.

  33. Francesco Petronella

    When I try to open the context menu rightclicking an Icon in Dolphin or in the Desktop, Dolphin/plasmashell crashes. This seems to happen only after a while the X server is on, even if I don’t do any operation. The crash window report a Segmentation Fault. Also, the KDEConnect plugin window in the panel always report:

    Errore durante il caricamento del file QML: file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:24:1: plugin cannot be loaded for module “org.kde.kdeconnect”: Impossibile caricare la libreria /usr/lib64/qt5/qml/org/kde/kdeconnect/ (/usr/lib64/qt5/qml/org/kde/kdeconnect/ undefined symbol: _ZTI21DevicesSortProxyModel)

    KDEConnect works fine anyway, with notification and all. Also this message and the SegFault can be eliminated doing:

    # slackpkg reinstall kdeconnect
    $ killall plasmashell && plasmashell

    just resetting plasmashell does nothing and you have to do every time you turn on the pc.

  34. Hristo Simeonov

    after last update from today of Slackware current, I have problem with kwin_x11. Some times stop working and Im unable to switch programs from task bar, need to switch in console (CTRL+F1) then to return back in desktop (CTRL+F7).

  35. zappalaus

    After updating my current today, I had problems with libXfont in my plasma 5.8.3. It does not work with libXfont 1.5, if it happens with the installpkg libXfont 2.2…..

  36. Hristo Simeonov

    Unable to make rsync on tree, always got:
    receiving incremental file list
    5 -> ../14.2/5

  37. Fabick

    Hi Eric, from the latest version of Plasma upgraded, from time, the system don’t permit to unlock the session after return from ibernation, for example. Give me this advice “open a terminal and give the command – loginctl unlock-sessions – to unlock the sessions”. But even with this procedure, often I need to reset server X. I think because there isn’t systemd 😛 There was a report about this bug, that seems to involve kscreenlocker : . What you think about?

  38. lm4u

    Works and looks very enjoyable.
    Thanks very much for your effort!

  39. alienbob

    Francesco, if you get that error you still have the KDE4 based kdeconnect package from Slackware installed. Remove that, and install kdeconnect-framework instead. The README instructs you to “removepkg kdeconnect”, apparently you overlooked that.

  40. alienbob

    zappalaus, there’s a new package in Slackware-current that apparently you overlooked. It is called “libXfont2”. Install it and your issues will disappear.

  41. alienbob

    Fabick no idea. If you think it is a bug, create a KDE bug report about it.

  42. alienbob

    Hristo, first check that you updated your Slackware correctly. If you use rsync on my repository, you need to rsync the full repository. The ./current/5 repository and the ./14.2/5 repository are the same, and in order to avoid double storage needs, I just use a symbolic link.

    If you still want to rsync only the ./current/5 repository then you can let rsync follow the symlink and download the actual files. For that to happen, you need to change the “rsync -a” command into “rsync -rlpLgoD”. The “-a” switch is shorthand for “-rlptgoD” and the only difference is that “-l” gets changed into “-L”.

  43. Fabick

    Sorry Eric, probably I haven’t explained very well. I don’t know if this is a bug or not. Would only know if, with the latest release of your Plasma package and Xorg v1.19.0 plus kernel 4.4.32 in current64, any other user have the same behavior with kscreenlocker, just to understand if this depends on the combination of the three, or is a particular problem given from my hardware configuration and the latest release. Thanks for all your work, as usual!

  44. Marcus

    Fabick I have the same problem afther upgrade to 5.8.3. I had to disable “lock screen on resume”

  45. Hristo Simeonov

    I figured out about screen freezing. That’s happened when I upgrade to latest libxcb from slackware-current and this lib also is used from kde5 so first time I was thinking the problem may be in kwin_x11. Error is:
    QXcbConnection: XCB error: 3 (BadWindow), sequence: 3340, resource id: 62957546, major code: 15 (QueryTree), minor code: 0
    QObject::connect: invalid null parameter

    and nothing on the screen is working until I switch to console and return back. It’s seems something in last upgrade of slackware64-current (xcb, x11) isnt working like before because last version of kde5 project work very well before I to upgrade x11 to 1.19.0

  46. Marcus

    it looks like a bug in libQt5

  47. alienbob

    If that is the bug, then upgrading to Qt 5.7.1 should fix it.
    Unfortunately I am currently travelling and unable to compile packages for my repository.
    Anyone affected by the bug can download the qt 5.7.1 sources and compile a package themselves of course.

  48. Mikel Nies

    I’m having problems with SDDM crashing. I can startx and plasma loads and works fine. When I set SDDM to auto login I do get to the desktop with init 4. But when I log off SDDM crashes again?

  49. Eduardo

    Hi Eric, I’m experiencing a bug which might be related to the Qt bug you mention. After logging in, the startup screen activates but at the end of the start screen the screen does not update; it still is a black “K” logo. I have to switch to a virtual terminal such as tty1 and back to see my screen.

    When using dual screens, the secondary screen shows up on time but the main screen keeps being blackened until I perform that virtual terminal switching.

  50. alienbob

    Mikel, sounds like a functional bug for a specific usage scenario. Please create a bug report at :

  51. alienbob

    Eduardo, I have had that issue for many releases (almost a year) and could not decide what piece of software was causing it. But since I left IBM and had to hand in my thinkpad I have not had this issue anymore (seems to be related to Intel graphics because I do not see this on Nvidia GPUs).
    However I have a new T460 thinkpad now (also Intel graphics, but Skylake architecture) which I bought myself, and that one does NOT have the bug.

  52. Mikel Nies

    I found out SDDM crashes because I’ve upgraded xorg.

  53. alienbob

    Try to find the errors that SDDM will be generating, they should point us in the right direction. Check out /var/log/sddm.log

  54. Mikel Nies

    The log isn’t much use. Don’t get more info then:

    Signal received: SIGTERM
    Error from greeter session: “Process crashed”
    Auth: sddm-helper crashed (exit code 15)
    Error from greeter session: “Process crashed”
    Auth: sddm-helper exited with 15
    Greeter stopped.

    And then it tries again. I assume I need to recompile SDDM because I’ve upgraded xorg.

  55. Mikel Nies

    A recompile didn’t help either. I burned the live iso with Plasma5 and I get the same black screen. So it has to be something else.

  56. Eduardo

    Thank you Eric. Will report the issue upstream and see what they can do about it.

  57. Gérard Monpontet

    sddm work here i have applied many fedora patch and consolekit diff:


    I have temporarily fixed the kde problem on radeon
    i use mesa-12.0.4 🙂

  58. Mikel Nies

    I’ve also solved my problem with SDDM. It turns out SDDM works after I disabled HiDPI to false in /etc/sddm.conf.

  59. K

    I’ve tried rsync files as mentioned in README:
    rsync -av –exclude=x86 rsync:// .
    but end up with dead link to 14.2. Is there any particular place where rsync command should be run?

  60. alienbob

    Hi “K”

    The “current/5” directory is actually a symbolic link to “../14.2/5” because the package sets for both Slackware 14.2 and -current are identical.
    Therefore, the rsync command in the README (which you used) will only download a dangling symlink, whereas adding a slash after the “5” will actually download all the requested content.

    Try this instead:

    rsync -av –exclude=x86 rsync:// 5/

    or perhaps a faster download URI:

    rsync -av –exclude=x86 rsync:// 5/

  61. K

    Thanks Alien, that worked for me. One more question, I have freshly installed Slackware 14.2 with out slackpkg or any third party repos configured (like ktown), however regarding to:
    “If you have my ‘ktown’ set of KDE 5_16.08 installed:
    – No further actions are needed.”
    Do I have it installed by default or not?

  62. K

    I’ve just installed new KDE as mentioned in README, but unfortunately after that have only white rectangle in the left upper corner with Bash prompt. What went wrong?

  63. K

    When I am trying to start KDE as root, then following errors appears:
    /usr/bin/startkde: line 156: qtpaths: command not found
    Loading stage “initial” 156
    /usr/bin/startkde: line 209: qtpaths: command not found
    startkde: Starting up…
    startkde: Could not start D-Bus. Can you call qdbus?
    Warning: Missing charsets in String to FontSet conversion
    Warning: Unable to load any usable fontset

  64. alienbob

    Probably you need a reboot first. The qt5 package which is part of the “deps” installs a profile script, and DBus needs to be restarted to pick up several new configuration files. A reboot is the easiest way.

    About your question “If you have my ‘ktown’ set of KDE 5_16.08 installed: No further actions are needed.” – you need to read all the way down. Those instructions are for the case where you have an older version of my ktown packages installed. If you just have Slackware 14.2 then you will not have any of my custom ktown packages and all those instructions about older ktown versions are irrelevant to you.

  65. K

    I have restarted as mentioned in readme file. This is how it looks:

  66. alienbob

    Well first, do not try to start an X session as root. Create and use a regular (non-root) account.
    Second, do you still have the error “qtpaths: command not found” even after reboot? In that case you did not install the qt5 package from the “deps” subdirectory.

  67. K

    I have installed all packages from deps/ as mentioned:
    # upgradepkg –reinstall –install-new x86_64/deps/*.t?z
    # upgradepkg –reinstall –install-new x86_64/deps/telepathy/*.t?z
    # upgradepkg –reinstall –install-new x86_64/kde/*/*.t?z

    This is what I’ve got:
    root@toshiba:/usr/src/5/x86_64/deps# ls /var/log/packages/ | grep qt

  68. alienbob

    You seem to have installed packages as intended. And yet the command “qtpaths” is not working as shown in your feedback “/usr/bin/startkde: line 156: qtpaths: command not found”? Or has that error gone now?
    Are you starting X in runlevel 3 (console) or 4 (graphical login)? In runlevel 3, use the “xwmconfig” program to select xinitrc.plasma as your default desktop (run the command as the user who will run “startx” next).
    And search for clues in your system logs. There is nothing else I can contribute from here because I can not see inside your computer.

  69. K

    xwmconfig – did the trick 😀 Thank you.

  70. BrianA_MN

    Hi Eric, I’ve upgrade from kde5_16.08 installed from the LIVESLAK 1.3 and after upgrading to KDE5_16.11 I’m getting a blank screen with Kwin_X11 -session 10addcd7a30001…. using 100% CPU. The odd thing is that KeePassX and ESET NOD32 which are in the autostart folder, both start windows and KeePassX allows me to use the keyboard to open my database, ESET shows the GUI startup screen then minimizes as normal. HP-Systray even pops up a small window indicating no system tray is available on the system. If I use ALT+TAB I see KeePassX. CTRL+ALT+F1 or F2 gets me a CLI login, and CTL+ALT+F7 takes me back to the blank screen. No other combination of mouse buttons or keys gets me a menu to work from.
    I’ve upgraded from the kde5_16.08 using the slackpkg+ commands and checked the conf to confirm ktown is priority A reboot without SDDM produces the same results. My current kernel is 4.4.34, but was getting same blank screen with 4.4.30. CAT of startx 2>1 | tee ~/startx.log only shows a GOT SIGHUP, which I’ll assume was result of my using CTRL+ALT+BACKSPACE to get back to CLI and halt X11. All files are correct to your KDE5_16.11 repository. Graphics is nouveau, so no proprietary video drivers. Would next step be to move aside the ~/.config/autostart/ folder (incase there is a mishaving widget)? Or is there something about not being able to upgrade from LIVESLAK which I missed? Your advice is appreciated. Hope the RHEL testing is going well. Cheers

  71. BrianA_MN

    Eric I should have been clear that the other DE/WM’s including LXQT and Lumina startx without trouble. It is only KDE that won’t start a menu. SDDM/Plasma (Failsafe) was tried and it also produced blank screen.

  72. alienbob

    Brian, you do not state it explicitly but I guess you are running this still on a Slackware Live USB key with persistence, and you upgraded the Plasma 5 packages on that USB key to the ones I currently offer in my repository?
    You could perhaps look inside /var/log/Xorg.0.log for clues.

    Also you should be aware that the script has a “refresh” parameter. With that “-r” and pointing it to the latest Plasma5 Live ISO, the script will refresh the content of the liveslak installation with the modules taken from the ISO file, while otherwise leaving your modifications untouched (persistent data, your homedirectory).

  73. BrianA_MN

    Hi Eric, Actually this is a HD installation. /var/log/Xorg.0.log of course has my newest Xorg WM/DE statements and nothing for the Plasma attempt which I tried to redirect with startx 2>1 | tee ~/startx.log but today I found the log in a ~/1 file (typo in command error). That file is large and I won’t flood this blog. I’ll study the file before posting again. Right off the bat I see a (EE) nv: module ABI version (20) doesn’t match server version (23) . Which I believe is because I’m using NVIDIA’s firmware but not their driver. I’ll work through the file, I also see a xset font path bad, and something about a serverauth missing. I’m surprised this doesn’t affect my other WM/DE’s but I’ll be back to you after clearing these simpler issues.

  74. K

    Can’t build gst-plugins-bad because of qt5:

    /usr/include/qt5/QtCore/qhash.h:958:31: note: suggested alternative:
    In file included from /usr/include/c++/5.3.0/utility:70:0,
    from /usr/include/qt5/QtCore/qcompilerdetection.h:991,
    from /usr/include/qt5/QtCore/qglobal.h:83,
    from /usr/include/qt5/QtQuick/qtquickglobal.h:43,
    from /usr/include/qt5/QtQuick/qsgtexture.h:43,
    from /usr/include/qt5/QtQuick/QSGTexture:1,
    from gstqsgtexture.h:25,
    /usr/include/c++/5.3.0/bits/stl_pair.h:96:12: note: ‘std::pair’
    struct pair
    Makefile:940: recipe for target ‘libqtsink_la-gstqsgtexture.lo’ failed
    make[4]: *** [libqtsink_la-gstqsgtexture.lo] Error 1
    make[4]: Leaving directory ‘/tmp/SBo/gst-plugins-bad-1.6.2/ext/qt’
    Makefile:830: recipe for target ‘all’ failed
    make[3]: *** [all] Error 2
    make[3]: Leaving directory ‘/tmp/SBo/gst-plugins-bad-1.6.2/ext/qt’
    Makefile:1361: recipe for target ‘qt’ failed
    make[2]: *** [qt] Error 2
    make[2]: Leaving directory ‘/tmp/SBo/gst-plugins-bad-1.6.2/ext’
    Makefile:954: recipe for target ‘all-recursive’ failed
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory ‘/tmp/SBo/gst-plugins-bad-1.6.2’
    Makefile:883: recipe for target ‘all’ failed
    make: *** [all] Error 2

    Would you like to continue processing the rest of the
    queue or would you like to abort? If this failed
    package is a dependency of another package in the queue
    then it may not make sense to continue.

    (Y)es to continue, (N)o to abort, (R)etry the build?:

    I have had the same issue with VLC, but finally I’ve installed it from your repo.

  75. K

    OK, nevermind. I don’t need that gst-plugin. However, this:

    has stopped working after upgrade to KDE 5.8:

  76. alienbob

    Advice for gst-plugins-bad:

    The error is caused by Qt 5.7, which requires C++11. You need to tell the compiler to use C++11.
    Add “-std=c++11” to the CFLAGS variable in the SlackBuild script and the compilation should succeed.

  77. BrianA_MN

    So the default xorg will try to start various drivers, including nv and fbdev, but this is not a problem. My solution was to follow my own advice and move aside (read rename) the ~/.config/autostart folder. There was some widget or shared autostart item from XFCE which was causing the plasma session to either halt or hang. I’ll try testing each of the old autostart items to find which one. It was not HP-systray because it is now showing in the task bar without issue. Hope this helps others. Looks great now.

  78. Gérard Monpontet

    just for info:

    kexi-3.0.0 (calligra-3.0.0)
    need breeze-icons compiled with

    because ‘kexi’ need breeze-icons.rcc, Which is not currently present in the ‘breeze-icons’ package 😉

  79. Pobby


    I uninstalled all packages as suggested in README.txt. I then installed the packages from ktown (latest) like this:

    slackpkg install-new
    slackpkg install ktown
    slackpkg upgrade ktown
    slackpkg upgrade-all

    However, some packages are now complaining that some libraries are missing such as libkactivites and libbaloofiles. Konqueror (file-browser) is missing the libbaloo for exampe.

    So I reinstalled all removed packages except kde-kdeconnect. Did I miss something?

  80. Pobby


    I again uninstalled all packages as suggested in README.txt. Then I rscyned: rsync://

    Still same problem.

    Am I using the correct mirror?

  81. Gérard Monpontet

    Hi, Eric, package ‘marble’ has syconfdir in /usr 😉

    need add this option:


  82. alienbob

    Hi Gérard – I will use that straight away on my next batch of packages, thanks.

  83. bam

    Thanks Eric!
    Would be sad if you drop Slackware 14.2 though..

  84. bam

    Hi Eric,
    seems like your kde repo for 14.2 is in inconsistent state now, can’t upgrade through slapt-get:
    For example, PACKAGES.TXT lists PACKAGE NAME: PyQt5-5.7.1-x86_64-2alien.txz,
    but there is not such package available, only old PyQt5-5.7.1-x86_64-1alien.txz

  85. alienbob

    bam, I think I may have to update my script for the first time in two and a half years. I am now using hardlinks in the repositories and the script does not handle those correctly.

  86. BrianA_MN

    Eric, for Slackware 14.2 x64, what are the dependencies for SDDM-qt under KDE 14.3? I’ve loaded libinput-1.6.3, libwacom-0.24, and libxkbcommon-0.6.1, along with qt5-5.7.1, but it still is giving me a blank screen on start with no keyboard or mouse input. Since I don’t have plasma loaded I selelct xfce in wmconfig before restarting in init4. I’m getting the same blank screen if I try the older SDDM (2014) from your respository. Don’t see any error in the or SDDM logs other than normal outputs. But I also don’t see a connect for SDDM to a screen. Hints or suggestions would be appreciated.

    I can get SLiM to work but with two screens it’s centered and doesn’t recognize there are two monitors. Can work with it, but really like the newer SDDM, which I hope Pat will add to next release of Slackware.

    Hm yes I’ve gone back to 14.2 base to ease my updating. Like the liveslak but wanted to avoid the “mess” you advised I get if I don’t upgrade KTOWN regularly with the -current base app updates. So decided to go back to 14.2 and keep it simple. Just miss the SDDM.

  87. BrianA_MN

    Eric, I found that if I downloaded your older SDDM-201140508git source and built local that it then worked. I picked this clue up from an older LQ comment on SDDM where they had to do the same, there is something about your 20140508git-x86_64 package that doesn’t work on my configuration. But I’ve built from source and everything appears to be working great, including showing me all three users. Of course it also showed plasma.kde for some odd reason? But I’ll find out where it is getting the session options from, too bad it isn’t from the same location as xwmconfig.

  88. alienbob

    BrianA_MN, X sessions are loaded from /usr/share/xsessions/ directory.
    On my Slackware64 14.2 installation, the latest SDDM package works as expected, if your installation gets stuck in a black screen, I wonder if you have all my packages installed or that there’s been some kind of mix-up with Slackware-current packages?
    Did you try recompiling sddm-qt5 package using my latest sources instead of going back to a prehistoric version?

  89. BrianA_MN

    Eric, thanks for the feedback and clue. I’ll try the recompile of sddm-qt today. The packages I noted earlier are the 14.2 versions, except for your qt5, sorry if that caused confusion. Could the issue be all that they need to be replaced with your’s? Are there other alien packages required besides qt5 and your sddm-qt src? Thanks

  90. BrianA_MN

    Eric which repository would I use to get the sddm-qt build script? I can find the older build but only packages for the sddm-qt. Thanks

  91. alienbob

    BrianA_MN – I can not help you with your confusion without more background.
    What version of Slackware are you running exactly? I.e. what is the URL of the repository you are using to keep your Slackware uptodate? And what is the URL of the ktown repository you are using for the Plasma5 packages?

    There is only one source location, from which I compile all packages (both for 14.2 and -current):

    Compiling sddm is exactly identical for a 14.2 or a -current system: after you downloaded all the sources and scripts you execute:
    # cd source/kde
    # ./KDE.SlackBuild plasma-extra:sddm-qt5

  92. BrianA_MN

    Eric, I’m on slackware 14.2 -64 from
    I DO NOT have Plasma5/KTOWN fully installed. I have selectively installed from the following as reported by ls /var/log/packages | grep alien

    First, as I write this I realize that the qt5 is for -current and I’ll remove and install the 14.2 version. Second, in the repository the SDDM version is 20140508git and there is not SDDM-qt version even under current. So either I don’t have all the minimum required dependencies for SDDM to work correctly or the Plasma5/KTOWN version sddm-qt (package only available) has many more dependencies, as listed in

    I did think to try another way and downloaded sddm-0.14.tar.xz from github and then modify the build script, but I received a error output of could not find package configuration provided by “ECM” (requested version 1.4.0) with the following names ECMConfig.cmake, ecm-config.cmake.

    I realize this is not a support forum. I have the older SDDM working for logins but not power.
    If it is not possible to install sddm-qt package without all the deps of Plasma5 then thank you for your time. I’ll try LQ or the IRC for sddm for further assistance. Cheers

  93. BrianA_MN

    Eric, I found and installed extra-cmake-modules to solve the ECM error problem. I’ve built sddm-0.12.0 release from git source with your old 20140508git sddm.slackbuild updated to point to later versions. But when attempting to build either 0.13.0 or 0.14.0 an error is thrown where it is trying to look for PAM. OUTPUT is
    — Found PkgConfig: /usr/bin/pkg-config (found version “0.29.1”)
    CMake Error at cmake/FindPAM.cmake:70 (message):
    PAM was not found
    Call Stack (most recent call first):
    CMakeLists.txt:74 (find_package)
    — Configuring incomplete, errors occurred!

    For some reason the slackbuild’s line to remove PAM isn’t recognized by the new sddm? Any clue you might shed on this? If not I now have sddm to release 0.12.0 Cheers

  94. alienbob

    I do not support partial installations of my Plasma 5 ‘ktown’ set, sorry. A *lot* of my time is spent on finding the correct and minimal set of dependencies that are required to make this complex software work.
    Many of the issues you (and others) have reported here are due to incomplete installations causing missing dependencies.

  95. BrianA_MN

    Thanks for responding. I’ll seek help from the sddm folks and LQ. For anyone else reading this blog, the sddm page indicates some dependencies, but also says that PAM and Systemd are recommended but their build script is suppose to accept PAM not present and will look to upower. Cheers.

  96. alienbob

    Please do not take the SDDM pages as your guidelines, they do not run Slackware. And LQ people generally do not run my Plasma 5.
    Use my Slackware build instructions, and patches, instead. I showed you how to build a sddm-qt5 package. Why is that so difficult? PAM is not required, systemd is not required.

    Its cmake script:
    Its patches: and the content of
    It’s post-compilation actions:

    That should give you the required pointers.
    Again, why the partial installation if you do not know what dependencies are needed?

  97. BrianA_MN

    Eric, Thank you for answering, when I wasn’t expecting anything further.

    I’m sorry if you were confused or frustrated with my questions. I am impressed with your persistent follow-up to help another Slackware user because I didn’t expect any further communication on this issue. I think we’ve been talking past each other on what dependencies and source to use. I know you are going way beyond the necessary support to most inquiries. I hope the following recap will give you a clearer idea of how I was reading your responses and doing my own research to resolve the issues I was having with SDDM, not expecting you to support an older stable installation. I realize your time and efforts are correctly focused on the next release of Slackware.

    To recap, my first question to you was “what are the dependencies for Slackware 14.2- 64 with KDE 4.13?” Your response was to use the source and rebuild. When I asked where the source was located you responded with a link that has a hierarchy that appears to be for latest KDE 5, which I’m not running so I search up the parent heirarchy for 4.13. I found that the “parent” hierarchy path had a 14.2 directory which had NO build or source or pkgs for sddm. The link provided had a /deps directory that appears to be the focus of Plasma5 builds. I thought your heirarchy was logically showing dependencies for a KDE version that I’m not interested in at this time. And to test that I looked at the and found sddm-qt only for /5/ and not for /4.13.2/. Not finding what I was expecting in the parent’s link and when searching your bear repositories I found available in the sddm build source I thought you were suggesting. I used the original build from the older git and successfully built the 20140508git package! YEA! That same slackbuild then successfully built 0.9 and 0.10 and 0.12 releases, although I had to install extra-cmake-modules at one point. When the slackbuild failed for 0.13 and 0.14 asking for PAM I determined there were more changes required to the slackbuild and sent my March 25 6:31 message. Knowing I have no reason to expect you to support your slackbuild or an SDDM for KDE 14.3 I was ready to move to the original programmers and other who might have ideas or suggestions.

    Again, thank you for your continued help. You have gone above and beyond my expectations for supporting my desire to install SDDM. I’m not a programmer and while I can locally build with .config, make &&make install or execute a slackbuild, I have to learn how to use patches on source to use what you’ve provided. Please don’t spend any additional time on this issue. I’m much more interested in your time on the next version of Slackware!
    Even if I continue to use the 0.12.0 version I’m getting the experience of SDDM for the next Slackware release.
    Cheers, Brian

  98. BrianA_MN

    Eric, Thank you again for all the support. I successfully have now built sddm-0.14.0! YEA! I thought I’d just leave this update for you to enjoy and smile, another non-programmer making slackbuilds with great assistance from the one and only AlienBob!

    I’ve modified the original slackbuild to include the pertinent parts (sorry I don’t need Dutch at this time 🙂 ) The patch has auth.diff commented out. If it is to be applied, it fails to apply the Passwdbackend.cpp change. I’ll simply try it with and without being applied and see what happens.

    Also, I notice that although I modified the slackbuild with the all the cmake modes you listed, including -DENABLE_QT4:BOOL=FALSE and -DENABLE_QT5:BOOL=TRUE, the build still used qt5 since it found it. I assume it is because it finds the QT5Test file and uses QT5. No matter I have qt5 installed so all should still work.

    Thanks again and Cheers.

  99. alienbob

    Hi Brian

    That is why I suggested to use the KDE.SlackBuild script framework and just run “./KDE.SlackBuild plasma-extra:sddm-qt5” to generate the sddm-qt5 package.

    To come back to your remarks: that ‘sddm-auth.diff’ patch is not used in my script because it is no longer needed. It is commented out in the file “./patch/sddm-qt5.patch”:

    # Fix a compilation error on passwd backend:
    #cat $CWD/patch/sddm-qt5/sddm_auth.diff | patch -p1 –verbose || { touch ${SLACK_KDE_BUILD_DIR}/${PKGNAME}.failed ; continue ; }

    The cmake parameters ” -DUSE_QT4:BOOL=FALSE -DUSE_QT5:BOOL=TRUE” force the use of Qt5 over Qt4. But the issue is moot, since SDDM will no longer compile against Qt4 as far as I know.

  100. BrianA_MN

    Thanks again for the clarifications. I’m beginning to understand and have now found under cmake –help the proper way to use –D [:]=. I was thinking it was “denable” like do not enable instead of -D cache Enable. 😉 my bad. The reason I didn’t use your first method was because I didn’t know how to easily replicate a whole repository locally? I today learned more about rsync and replicated your first reference. This of course provided the entire directory and I needed only small parts of it. Thank you again for your help! It is always a learning experience, literally. For example I’ve had this open for 4 hours, because each time I got ready to respond I thought, wait I can look that up or learn how to do that, ex cmake commands and rsync. Truly a learning experience with a little guidance from you and I’ve made huge strides in programming slackbuilds, how to use cmake, how to use rsync, how to use git, how to search the HOWTO’s and howto properly use man. That’s a lot of learning from a simple desire to use SDDM. THANK YOU!

  101. alienbob

    Brian, for your reference: I have example rsync commands in the README of every Plasma 5 release that show you how to download the sources/scripts, or how to download packages.

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 ↑