My thoughts on Slackware, life and everything

KDE Plasma 5 August 2020 release for Slackware

New Plasma5 packages for Slackware-current are ready for download & installation. I skipped July (holiday season) and so here is KDE-5_20.08 aka my August 2020 release. Be sure to read the upgrade instructions very carefully to prevent  breakage, because starting with my June batch the goal is to remove Slackware’s ConsoleKit2 and replace it with elogind!.

It would not harm if you (re-)read my previous blog article about Plasma5, “Replacing ConsoleKit2 with elogind – first steps“. It has a lot more detail about the reasons for this move as well as guidance on using the Wayland Window Manager (as a test) instead of regular X.Org. Note that Wayland sessions still need a lot of maturing and X.Org will remain Slackware’s default choice.

A repeat from that article: with elogind as the session/seat manager instead of ConsoleKit2, you’ll see some new behaviour. A quite obvious change: if you run ‘startx’ or ‘startkwayland’ at the console, you won’t see a VT (virtual terminal) switch. In the past, your console TTY would usually be tty1 but your graphical session would start on tty7 and you would automatically be switched from tty1 to tty7. This is no longer true – the graphical session will re-use your console TTY.
SDDM is still starting on tty7 but only because I make it do so via its configuration file.

What news is there to tell about KDE-5_20.08?

This August ktown release contains the KDE Frameworks 5.72.0, Plasma 5.19.4 and Applications 20.04.3. All this on top of the Qt 5.15.0 in Slackware-current.

The ‘deps’ section got a bit smaller again this month:

  • pcaudiolib, espeak-ng, hack-fonts-ttf, noto-fonts-ttf, and noto-cjk-fonts-ttf were moved into the actual Slackware distro. Things are progressing nicely in that regard.
  • flite has been removed since Pat decided we will go with just espeak-ng.
  • a new package ‘pipewire’ was added as a dependency for krfb and xdg-desktop-portal-kde.
  • The elogind-aware dbus package was upgraded to match the Slackware version.
  • Finally, qca-qt5 was upgraded and I recompiled mlt (to fix the broken kdenlive) and speech-dispatcher.

Frameworks 5.72.0 is an incremental stability release, see: A new ‘kdav’ source tarball got added but that is actually the same package you’ll find in KDEPIM. Next batch, the actual kdav package will be built from Frameworks sources.

Plasma 5.19.4 is a further increment of the 5.19 cycle (5.19.5 will be the last, in September). See and if you want to read more about the goals for 5.19 you should check out .

In plasma-extra In plasma-extra I rebuilt sddm-qt5 to install man pages correctly, and upgraded plasma-wayland-protocols and wacomtablet.

Applications 20.04.3 is an incremental bug fix release, see also

For applications-extra, I updated digikam, krita, libktorrent and ktorrent, and skanlite.
Note that the size of the digikam source tarball ‘blew up’ due to the addition of new neural network facial recognition data files, but the actual package ‘only’ grew from 97 to 108 MB.

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

KDE Sources:
Not so visible but important nevertheless is this month’s contribution of Patrick Volkerding who validated all the KDE slack-desc files and enhanced/polished a lot of them. He also cleaned out the ‘patches’ directory and removed all the obsolete patches that are not being applied anymore. As you also will have noticed, Pat is slowly picking packages out of my ‘deps’ and adding them to Slackware. Even espeak-ng which I had not expected to happen.

Where to get KDE Plasma5 for Slackware

It should be obvious, but these packages will not work on Slackware 14.2. The old (KDE 5_17.11) Plasma5 packages that were still in my ‘ktown’ repository for Slackware 14.2 were removed in May 2020 because they were un-maintained and had security issues.

Download the KDE-5_20.08 for Slackware-current from the usual location at or one of its mirrors like .

Check out the README file in the root of the repository for detailed installation or upgrade instructions.

BIG FAT WARNING: Read these README instructions carefully if you do not yet have elogind installed (i.e. if you did not install the ktown June 2020 release previously)!
In short:

  1. UPGRADE TO THE LATEST slackware-current first.
  2. Then, REMOVE the ConsoleKit2 package if you had not installed my June ktown batch before.
  3. Next, install or upgrade the KDE5 package set.
  4. Change to directory /usr/share/sddm/scripts/ and move the & files into place (remove the .new extension) after carefully checking that you are not overwriting your own customizations in the Xsession & Xsetup scripts. Note: because “slackpkg new-config” only looks inside the /etc/ directory it will miss the two scripts in /usr/share/sddm/scripts/.
    You’ll still have to manually check /etc/ for some critical *.new files that need to be put into place if you are not using slackpkg (which does this *.new check at the end of its run).
  5. Finally, REBOOT.

Development of Plasma5 is tracked in git: and this month’s development took place in the ‘elogind‘ branch. I will fold these elogind developments back into the master branch soon.

A new Plasma5 Live ISO will be available soon at (rsync:// with user/pass being “live/live” as always.

Have fun! Eric


  1. Eduardo

    Thank you Eric! Very nice to see that Pat validated the slack-desc files. Downloading now.

  2. Richard Herbert

    Hi, Eric. Thanks for the update! As is my wont, I jumped on it quickly. The first thing I notice is there are no shutdown options in the Leave menu. I tried disabling and re-enabling the “Offer shutdown options” setting in Sytem Settings. No change. I had already installed the June update of KDE Plasma, so the necessary files were already in place in /usr/share/sddm/scripts. Not sure where to look, but will keep trying to figure it out.


    • Richard Herbert

      Closer to a solution:

      upowerd[11635] trap int3 ip:7ffb4d72bfc5 sp:7ffe97ff17e0 error:0 in[7ffb4d6f3000+7e000]

      • Dariusz Brzezinski


        I have also no shutdown options in the Leave menu. Additionally the battery is not recognized (no batteries available).

      • Deny Dias

        Thanks Eric!

        Same upower issues here:

        $ upower -e
        (upower:3765): libupower-glib-WARNING **: 07:30:27.629: Couldn’t enumerate devices: Message recipient disconnected from message bus without replying
        (upower:3765): UPower-WARNING **: 07:30:27.630: failed to enumerate: Message recipient disconnected from message bus without replying

        None of the power management features works as they used to: battery indicator labeled with a red X, no display dim, power management tabs in system configurations gone, shutdown options limited to end session and such.

  3. Gerardo Zamudio

    Thank you for hard work, Eric!

  4. Francisco

    Hi Eric,

    Glad to see the transition process inside Slackware to KDE5.

    How is this internal Slackware process to finally have KDE5 in an official Slackware release?

    Is there a Slackware Committee to approve and define Slackware roadmap for future releases?

    Has Pat used this KDE5 Slackware?

    Thanks again for your contribution and for insisting on this changes.

  5. Regnad Kcin

    works good.

  6. Tom

    Thanks Eric for the update. I have a problem with ktorrent. It seems to start (blue circle spins) and then nothing. ps -ef shows that ktorrent is running but there is no gui. Also, Pat upgraded Polkit but when I install your new plasma5 it down grades it to 0.16 from Pats 0.17. Is this the problem? If I start ktorrent from the command line as me I just get back to my prom/home/tom# ktorrent
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    QStandardPaths: wrong ownership on runtime directory /run/user/1000, 1000 instead of 0
    “Session bus not found\nTo circumvent this problem try the following command (with Linux and bash)\nexport $(dbus-launch)”pt. If I try it as root I get –

  7. alienbob

    I had asked Pat if anything disruptive would be added to -current this week when I prepared for a new set of Plsama5 packages and he said he did not.
    However, I think that:
    l/mozjs60-60.9.0esr-x86_64-1.txz: Removed.
    l/mozjs68-68.11.0esr-x86_64-1.txz: Added.
    … may be pretty disruptive. If you removed mozjs60 from your computer while keeping my patched polkit-116 package I do not know what happens.
    My laptop is still not up to date but the desktop has the latest Slackware Plasma but with the older mozjs60 package (I upgraded right before the update in -current of “Fri Jul 31 22:00:05 UTC 2020”) and it has the shutdown/reboot menu present.

    Perhaps an update of polkit in my Plasma5 package set would help.

  8. Janis

    Thank you, Eric!

  9. alienbob

    The issues with the missing reboot/shutdown and ktorrent not starting its GUI are both not occurring after I remove mozjs60, install mozjs68 and compile a polkit-117 package with elogind support.
    So I will provide an updated polkit hopefully somewhere later this weekend.

    • Dariusz Brzezinski

      Thank you Eric for your great work.

      Returning to the mozjs60 also fixed the battery not recognized bug. This temporarily solution is good enough until the new polkit-117 package.

  10. alienbob

    I have updated polkit in the ‘ktown’ repository to 0.117 so you all can safely do a normal Slackware-current upgrade now.
    By the way, mozjs60 and mozjs68 packages can co-exist on your computer.

    • Richard Herbert

      Thank you so much, Eric! That did it. Shutdown and Restart options are back. “Somewhere later this weekend”, indeed! 🙂

    • Deny Dias

      That did the trick, although I’ll keep mozjs60 living together with mozjs68 for a while.

      Thanks for the quick fix, Eric!

  11. Alex


  12. pet_k

    Thanks for a perfect work!

    After update i have a problem with kdevelop from package kdevelop-5.5.1-i586-1alien:
    /usr/lib/qt5/plugins/kdevplatform/33/ and
    /usr/lib/qt5/plugins/kdevplatform/33/ – – not found (

    Please upgrade and rebuild kdevelop* packages in your repository.

    Many Thanks!

    • alienbob

      Unfortunately that will have to wait a bit.

      • pet_k

        Thank you, Eric!

  13. Eduardo

    Hi Eric! Upgraded and everything went ok except for the lack of shutdown/poweroff options. Upgraded to the new polkit and everything is OK again. Thanks for providing us an excellent implementation of Plasma 5!

  14. Dave

    Legend ????

  15. Eduardo

    Hi Eric,

    Are the font packages provided by Slackware and yours different? Right now there’s a subtle name difference (yours use “font” while Slackware use “fonts”). It is safe to replace your font packages with the ones from Slackware?

    Thanks again for providing Plasma,


    • alienbob

      What fonts Eduardo?

      • Ricardo

        Eduardo is probably refering to you packages hack-font-ttf and noto-cjk-font-ttf, Slackware’s packages are named hack-fonts-ttf and noto-cjk-fonts-ttf.

        I removed your packages and installed Slackware’s versions and besides some difference in the size of some fonts (most noticeable in Akregator’s feeds and some websites) they’re working just fine for me.

        • alienbob

          Hm, then I should update the README instructions and add an explicit removal of my font packages.

          • alienbob

            Also interesting fact: my noto-font-ttf package contained a lot of fonts that are not found in the package ‘noto-fonts-ttf’ which landed in Slackware. I’ll have to check with Pat.

  16. Henry Pfeil

    Now my Wacom Intuos behaves just like in Windows10, relative mode no longer works. My arm gets tired playing speed-kshisen, instead of keeping my palm in place and moving the stylus with short finger motions, back to the old forearm swing across the full tablet.

    • alienbob

      The wacomtablet package was updated – if that is the cause then perhaps look for bug reports there, or create a bug report yourself? I do not own one so I can not test.

      • Henry Pfeil

        No worries, I built wacomtablet-3.2.0 against the updates. Works as advertised. Don’t know what they did to break Relative Mode. A recent change for 3.3.0 deals with empty members of a string list. How they can possibly get empty value in a string list is left as an exercise. Maybe a string value isn’t checked before appending to the list?

  17. gegechris99

    Thanks again for the updated KDE 5 packages. I was a bit late to the party so I directly picked up the corrected polkit package. As a consequence, my upgrade went smoothly 🙂
    Regarding Noto fonts, after a quick look, the Slackware package does not contain any UI fonts (except for NotoNaskhArabicUI but it looks like an omission), nor any font whose name doesn’t start with Noto (Arimo, Cousine, Tinos) and it has a new NotoMono font that was not available in the ktown package.

  18. cabrageo

    I missed the new dependencies upgrading from June release and yes, it broke.
    Back to normal after getting slackpkgplus to fetch those dependencies, thanks for the good work.

  19. chrisretusn

    Awesome job Eric. I updated yesterday morning, all is well.

  20. Simon

    Thank you for your work, really appreciate it!

  21. Aleksandras

    Does it works correctly with NVIDIA 390.138 driver? Installation of previous plasma with elogind had some problems with animation.

    • alienbob

      Aleksandras are you referring to Wayland sessions or do you have issues in a regular X.Org session?
      My desktop uses the 440.100 version of the Nvidia drivers (my card is new enough not to need the legacy drivers) and I do not have issues, but I do not use Wayland myself.

  22. wirelessmc on LQ

    Hi Eric, This is a continuation of the last comment I left on the “Pam Landed…” thread. My system is a Lenovo ThinkPad with Intel Graphics chip so I’m guessing the pre-setup instructions regarding Nvidia mode-setting is not applicable on this system. It will however be applicable on the KDE4 Desktop I referred to that also has an older Plasma install on it since it does have an Nvidia GPU.

    The question(s) here is regarding gpg key and the KGpg desktop app which doesn’t launch any more. Instead I have to run ‘kgpg -k’ from the command line. I tried resetting the old key because I get a Pop-Up on my user login “Error when attempting to decrypt the wallet kdewallet using GPG. If you’re using a SmartCard,…& GPG error was No secret key”

    So upon running kgpg -k (which does launch) I tried resetting my old pass phrase but it wouldn’t let me. So some guidance here would be appreciated.

    • wirelessmc on LQ

      I should also state that I tried disabling kdewallet as root and that doesn’t help. elogin seems to know about my old gpg pass phrase since it gets me to the change pass phrase window. It just exits saying it can’t change it with no explanation of why.

  23. Widya Walesa

    Some changes in build ordering for frameworks (maybe after 5.73?):

    * kwayland needs plasma-wayland-protocols

    * kdepim-addons will build an import tools if akonadi-import-wizard is available

    * kinfocenter needs to symlink some UI binary from systemsettings

  24. wirelessmc on LQ

    Rightfully unanswered with such a trivial question 🙂

  25. wirelessmc on LQ

    Ok I just started Wayland for the first time. WOW! Is it me or is the graphics way snappier and so much sharper than X?!?!
    Awesome Eric! Thanks so much for your efforts. I think this fixes a bug with an old client that can only run with old X (32-bit) libraries. Thanks to multilib too!

  26. niko

    Hey Eric, thanks a lot for the update! I am a bit late to it. I was looking at the changelog for slackware and I saw there was recently an update in boost which happened after you released your plasma packages. I was wondering if your packages would be compatible with the new so boost library and if it’s safe to get the latest slackware64-currenty and your plasma 5, or it’s better to wait for the next release of plasma 5?

  27. wirelessmc on LQ

    Hi Eric, I have successfully installed the latest August package on two machines now. The first was a Lenovo laptop with an Intel 520 GPU and the second was a desktop PC with an Nvidia GPU. The first install went smoothly and I was able to bring up the KWayland session with no issues. In fact it fixed some things with on old X client which the newer X11 libraries didn’t handle well. I was delighted about this!
    The second install didn’t fare as well even though I was keen on closely following every step of your installation instructions. I passed the ” nvidia-drm.modeset=1″ option in my elilo conf and checked the running process to make sure it returned “Y” as you suggested. There are some things like sound issues even in the X session but the KWayland session (which will at least starts) is unusable due to horrendous mouse and keyboard hysteresis. So my next move on this is to try a complete de-installation, removing any kde4 packages that might still reside and then starting from scratch. If you can think of anything else to try I will certainly entertain that.

    • alienbob

      As far as I am concerned Wayland is not a serious contender to a replacement of X.Org. But YMMV.

      • wirelessmc on LQ

        Your perspective may be true today. Hopefully in the future Wayland will mature to the point where it does become a contender to X.Org. In any event I am grateful to you (and the KDE developers) for spending so much time and effort bringing it up on Plasma. I will continue using it till I find I just can’t get around an issue or a bug.

  28. wirelessmc on LQ

    Just an update to above – the install on system#2 with Nvidia GPU. It turns out that whatever is causing the mouse and keyboard hysteresis -rendering KWayland unusable- is associated with my user account. I created another user account on that system and KWayland runs without issue on the second account. Unfortunately I found all this out after the tedious chore of completely uninstalling all Plasma/KDE5 related packages and then doing a full reinstall.

    Now I need to do some detective work to find out what possibly could be specific to my user configuration that causes the mouse and keyboard issues. Any thoughts/suggestions would be greatly appreciated.

  29. Deny Dias

    -current l/qt5-5.15.1 does bite. Plasma will not start after this upgrade is applied. To workaround that I had to downgrade to qt5-5.15.0 available at:

    • Richard Herbert

      Thanks loads for the heads up, Deny. September KDE Plasma update anyone? 😉

      • alienbob

        I am done with Plasma5 updates until Pat incorporates Plasma5 into Slackware. Then I’ll provide the bleeding edge plus the stuff that did not make the cut. Until then, go with the flow and upgrade wisely.

    • Dave

      Interesting, no issues here yet with Plasma and qt5-5.15.1.

      • Richard Herbert

        No issues here either, Dave. Maybe Deny should try reinstalling qt5-5.15.1 after downloading again? So, no need to blacklist qt5. Good to know. 😉

        • Deny Dias

          I had no luck. First tried upgradepkg, then removepkg/installpkg. Neither did the trick. With qt5-5.15.1, after session logon with sddm, plasma starts to load, wallpapers appears, then taskbar flash in the screen and all becomes black, with no taskbar and no wallpaper. krun, yakuake and other apps loads fine though. It’s just the desktop components missing.

          I’ve added qt5, qt5-webkit, PyQt5 in greylist for know. So far, so good. Let’s see how long it lasts.

          • alienbob

            Sounds like plasmashell crashes for you. If you have a terminal open could you try running:

            kquitapp5 plasmashell && sleep 3 && plasmashell

            and then watch the output while the desktop user interface should restart. Perhaps you’ll see what the culprit of your issue is.

          • Savo

            I was having the same problem for me it was the event calendar widget causing plasma shell to segfault. I renamed it to get my desktop back then upgraded it now everything is good.

            Use krunner to start a Konsole and run plasmashell to get an error to work with.

  30. alienbob

    I upgraded my Desktop PC which is powered by a Nvidia card and uses its binary drivers.
    I am now fully up to date on -current as of 10-Sep-2020 running a 5.4.64 kernel and matching nvidia-kernel driver. I use runlevel 4 so I was greeted with the SDDM session manager after reboot, as always.
    It took a little longer to get from the black Plasma starting screen with the revolving circle to my desktop, perhaps because some cache data was being re-generated. But the desktop showed itself and I have not seen a glitch or any other problem since then. Typing this in Chromium, in my Plasma5 session.

    • Deny Dias

      I’m glad it works fine for you and the others, Eric. I’m also running with “fully up to date on -current as of 10-Sep-2020 running a 5.4.64 kernel”, except for qt5-5.15.0 (I’ve also pinned qt5-webkit and PyQt5, but they are in their most recent versions from -current changelog). Any attempt to upgrade it to qt5-5.15.1 brings the issue back. In my case, I’m running with intel drm, which may be the culprit as when trying qt5-5.15.1 plasma seems to crash when enabling compositing effects and no other qt app will have the fancy compositor stuff. Everything is back to normal as soon as I revert to qt5-5.15.0. Anyway, thank you for your report.

      • Deny Dias

        Just to let whoever might be facing a similar issue, the culprit in my case was an old, messy ‘~/.config/plasma-org.kde.plasma.desktop-appletsrc’. This file controls plasmashell behaviors. plasmashell is the “desktop program” of plasma. Move that file away then restart the session. You’ll loose all your desktop settings, but at least you’ll have a desktop to configure.

        • alienbob

          Thanks Deny, how did you figure that one out? By restarting the Plasma shell in a terminal and inspecting the output text?

          • Deny Dias

            Kinda. I didn’t see your message in time, but thanks for that anyway. I’ve set runlevel to 3, startx and inspect /var/log/Xorg.0.log. When I found that plasmashell was the one being interrupted… It turns out that plasmashell was working fine until it tries to load an outdated plasmoid: Event Calendar ( Then I removed its references from the former plasma-org.kde.plasma.desktop-appletsrc, manually updated the plasmoid to the newest version (the GUI update function didn’t work for an unknown reason, so I removed the old one, download the latest version from kde store, run ‘plasmapkg2 -i eventcalendar-v69-plasma5.13.plasmoid’), added it again to my taskbar and all is well now with qt5-5.15.1, including the plasmashell and the once faulty plasmoid. I already unpinned qt5, qt5-webkit, PyQt5 to keep “going with the flow and upgrade wisely”. 😉

    • Janis

      I updated just now to the .08 from .06. What I noticed – for some reason there is some 30 sec delay between the entry of the password and running desktop (it was not the case with .06). Do you have an idea where/how to look for the reason of the delay? In some old post I found that similar delay was caused by KDE querying Bluetooth devices, but seems it has been solved few years ago. (I have NVidia card with binary drivers)

      • alienbob

        Hi Janis. I have no idea what could cause a 30-second delay. I do not experience it myself, also you are the first to report this.
        FYI, I am running Plasma5 on laptop (Intel GPU and opensource driver) and two desktops with a Nvidia GPU, both using a Nvidia binary driver.

  31. acidtripper

    Hi eric.
    Having problems with polkit, restart, shutdown, etc.
    Managed to solve it using your slackbuild . rebuilt polkit against mozjs. Using polkit 118 from pat’s repo. Of course with elogind enabled and your patch.

  32. Henry Pfeil

    Is Pat working on upgrading kde/plasma? The only activity in ktown this month was the addition of deps/mozjs68. Slackware-current now has l/mozjs78. Is that backwards compatible with polkit? Is polkif-0.117 even needed, since current now has l/polkit-0.118?
    -Inquiring Mind

    • alienbob

      As I stated before, I have stopped providing updates to Plasma5 in my ktown repository. It’s up to Patrick Volkerding to show that he is willing to add Plasma5 to Slackware. If he declines, then that will be the end of Plasma5 for Slackware as provided by me and someone else can pick up the pieces. I am fed up with waiting for the dead KDE4 to be replaced with something that is modern. I have better things to do.
      If he does add Plasma5 to Slackware, then hooray.
      It is likely that he will not use all of the packages I have in my ‘ktown’ repository, because of the size of them all combined. Once I know which ones he leaves behind (thinking of digikam, krita, and other packages in applications-extra) I will keep providing updates to these in my (then slimmed-down) ‘ktown’ repository.

    • acidtripper

      Hi henry. Read upwards. Polkit needs to be rebuilt, if you need i have a package.
      Regarding Pat i don’t have that information.

  33. Henry Pfeil

    Thank you for your clarification. If there is a compelling reason to upgrade, I can use the kdesrc-build git repository. As for now, everything just works. Slackware-current kde has remained static since 2018, which is pretty-much useless, as is that 2016 edition of kdei.
    Thank you for all your work in Ktown! Time to move on.

    • alienbob

      The polkit in ‘ktown’ is built with an elogind patch. The polkit in Slackware does not have elogid support. There should not be any reason to update polkit at this point in time (which is why I added mozjs68 to the ‘ktown’ repository).
      If you wanted to upgrade polkit regardless, the best way is to do that using the ‘ktown’ SlackBuild and patch ( and the latest polkit tarbal instead of the Slackware scripts – and thus ensure that your new poikit will also have elogind support.

  34. Armin Herzer

    Hello Eric,
    when using 0050-multilib I can not login as user live into Plasma5 after booting because this does not exist. Yesterday I had some time to find out why. It looks like there is a file /etc/passwd in 0050-multilib and that file doesn’t have a line ‘live:x:1000:100:Slackware Live User:/home/live:/bin/bash’ (and it looks like this file will overwrite an existing /etc/passwd, which obviously comes from 0099-slackware_zzzconf, that you have when you boot without 0050-multilib). I created a new 0050-multilib without /etc/passwd and booting with it results in no login problems for user ‘live’.

    • alienbob

      Oops, I need to fix that. Thanks Armin for reporting the issue.

      • Armin Herzer

        No Problem. I saw yesterday that 0020-slackware-plama5alien, 0010-slackware-a and 001-slackware-l also contain /etc/passwd or /etc/passwd~ files…

    • alienbob

      The problem seems to be in the converted openldap-compat32 package. I will update the compat32-tools and then re-generate my multilib compat32 packages for slackware-current, then re-generate the squashfs module.

      • Armin Herzer

        Thanks for fixing this!!!

  35. bam

    To all of you, Slackware-lovers 🙂

  36. LoneStar

    I saw you’ve said more than once that you didn’t use the alldeps.SlackBuild script anymore for building Plasma deps. So, if you don’t mind saying, what did you use to keep track of what should actually be built as deps?

    • alienbob

      I had two scripts, alldeps.SlackBuild and updates.SlackBuild, that were nearly identical.So I removed one and kept the other.
      The SlackBuild mainly documents the build order but it says nothing about what program is a dependency for what KDE software.
      As a packager, every time KDE releases new software or new versions of their sopftware, I need to inspect the source configuration options and documentation for clues about updated or new dependencies and then act on those facts.
      Sometimes, a dependency is optional and I discuss with Pat whether he would want that as a part of future Slackware fuinctionality; and sometimes a depencency is mandatory and I have no choice but to add that new dep to the ktown source tree.
      And sometimes a new dependency is voted down by me and/or Patrick (i.e. we do not want this in Slackware) and then this decision results in dropping a KDE package from our distribution (like what happened with kpatience and others).

  37. Janis

    Ha haa! It finally happened!

    “Welcome to vtown, volkerdi’s friendly takeover of alienBOB’s ktown Plasma 5
    packages! Enormous thanks are due to alienBOB for maintaining and leading
    testing of Plasma 5 on the side, even as I wore out his patience (and likely
    others as well). …”

  38. acidtripper

    Hi there, somebody remember the fix for plasma and nvidia binaries?
    I’m getting this error:
    20.158] (EE) Failed to open authorization file “/var/run/sddm/{e1136050-d10a-4df3-82cf-3334199e3d7c}”: No such file or directory

    • alienbob

      Try adding “nvidia-drm.modeset=1” to your boot commandline. I use Nvidia with Plasma5 on this desktop I am typing on, and that is in my lilo.conf.

      • acidtripper

        I have just checked on my laptio, which has i915 and sddm is neither starting.
        I’m on slackware current, did upgrade packages as methioned method, as we were doing some time ago with ktown.
        Have rc.haveged started, rc.elogind started, rc.Consolekit2 disabled and also tried removing it.

      • acidtripper

        Found the solution, there were some pam modules Missing. It’s also solved upstream on vtown.

        Everything working as expected now.

        Thanks!, this is a happy day, at least for me.

        kind regards

  39. acidtripper

    Im using grud, tried adding these to /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT=”quiet nvidia-drm.modeset=1″
    the did grub-mkconfig -o …

    Doesn’t seems to work here, im suing nvidia binaries:

  40. acidtripper

    homeserver/etc/modprobe.d # modinfo nvidia-drm
    filename: /lib/modules/5.4.65/kernel/drivers/video/nvidia-drm.ko
    version: 450.80.02
    supported: external
    license: MIT
    srcversion: 2FCD797E8D0529B62813516
    alias: pci:v000010DEd*sv*sd*bc03sc02i00*
    alias: pci:v000010DEd*sv*sd*bc03sc00i00*
    depends: drm,drm_kms_helper,nvidia-modeset
    retpoline: Y
    name: nvidia_drm
    vermagic: 5.4.65 SMP mod_unload
    parm: modeset:Enable atomic kernel modesetting (1 = enable, 0 = disable (default)) (bool)

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 ↑