My thoughts on Slackware, life and everything

Month: December 2025

KDE Plasma 6_25.12 for Slackware-current

A couple of days ago, I promised to use my holiday to come up with packages for KDE Plasma6.
Today I finished compiling packages for 32bit and 64bit Slackware-current and uploaded a fresh package repository to my ‘ktown‘. The name seems to stick with people, even when it has not seen activity for two years, so I will keep calling it ‘ktown‘.

You will find these packages at the origin location: https://slackware.nl/alien-kde/current/testing/ together with an expansive README which will help you remove KDE Plasma5 from your Slackware-current computer and install the ‘ktown‘ version of KDE Plasma6 instead.

I just went through the process and this is the first time that I am actually running and using KDE Plasma6 on my production laptop:

I did not have to remove any kind of configuration from $HOME and merely had to delete a couple of obsoleted system tray elements.

I also switched to Wayland instead of X11 and to be honest, that is working better than expected and even better than the good old X11 session. For instance, suddenly I can play 4K video in VLC without stuttering. And the laptop’s  Synaptics touchpad was not found at all in the X11 session (must be a bug because I had been using it for 9 years in Slackware KDE)… while it works perfectly in the Wayland session.
The thing that I miss is the Latte Dock which was dropped from KDE Plasma. Having these MacOS-like ballooning application launcher icons floating at the bottom of my screen always impressed my friends, but it was also extremely powerful in the way I could manage my favorite applications. In Plasma6 I created an auto-hiding QuickLaunch panel at the bottom of the screen but it looks dull compared with the Latte Dock. Shame.

My intention is to keep this new Plasma6 package repository in a ‘testing‘ state as reflected in the repository URL. I expect that there’s stuff that does not work as it should and I would like you all to help in testing and stabilizing the packages. When KDE Gear 26.04 releases in April 2026 I expect that the few remaining Qt5 based KDE applications will finally have been ported to Qt6. By that time, I want to promote the repository from ‘testing‘ to ‘latest‘ and that will then reflect in the repository URL.

If you would look at the content behind the ‘latest‘ repository right now (https://slackware.nl/alien-kde/current/latest/) you will see that it is pointing to a single left-over package for KDE Plasma5 (Slackware 15.0): ‘phonon-vlc‘, a backend for Phonon that requires VLC media player. By the way, I renamed that package to ‘phonon-backend-vlc‘ for Plasma6 to be in line with the Slackware naming convention for these backends.
In April 2026 that repository will get a new  ‘stable’ URL to reflect that it is meant for the stable release of Slackware.

If you want to peek at the source code management, I track everything in a git repository. You will find the 6_25.12 branch at: https://git.slackware.nl/ktown/
A word of thanks to LuckyCyborg who maintained a fork of my ‘ktown‘ during 2024/2025. He never contacted me about this but I was made aware of his activities. I checked out his scripts last week and there were some improvements he came up with that I have incorporated into my own sources. See the git commit message for more details.

I suggest that you try these Plasma6 packages out yourselves! Please leave your feedback in the comments section below.

Enjoy the end-of-year festivities and all the best for 2026! Let’s hope that Slackware merges Plasma6 before the end of 2026.
Cheers, Eric

Enjoy the holidays!

We’re at that unique time of the year that I can work on something that is not trivial and requires long-term focus to succeed.
The festive season is upon us all, which means (not counting family diners and birthday parties) that I have two weeks to revisit all those ideas and plans I cooked up in 2025 and finish as many of them as possible. Otherwise it’s simply waiting for the next Christmas holiday to continue.

 

So what’s brewing in December 2025? To start with, a lot of paint jobs here in the house that are waiting since May when we finished going through a home renovation.

But I am also working on the resurrection of KDE Plasma6 for Slackware-current. Two years ago after releasing a Beta version of Plasma6 as a live ISO image, life took another turn and Plasma6 moved to the TODO list. I wrote about that period on some occasions.
But I think (or at least hope) that having a Plasma6 ktown out in the open and available for testing, will nudge Patrick into merging this into Slackware-current eventually. I’d rather have him focus on the other stuff that blocks a release, since I’ve shown and proven that I can maintain a ‘ktown’ out-of-tree.
Patrick and I discussed it, he sounds interested, not saying it is going to happen, but no risk, no reward, right? I promised that I would maintain a Plasma6 ktown during 2026 but not after. I got burnt with Plasma5 years ago, not going to repeat that. Ideally i’ll keep it going until that time that Plasma6 replaces the ageing Plasma5 in -current in 2026. And if it does not happen, someone else can copy my ‘ktown’ sources and continue from there.

I have a working Plasma6 and I’m now fine-tuning the scripts (I want everything to be built correctly, using the right dependencies) and will update my server’s ‘ktown’ package and source repository and also the git repository on https://git.slackware.nl/ktown once I am satisfied with the results.

Until that time, all you get is a screenshot.

Enjoy the holidays! Be safe and be there for your family and friends.

Eric

Building Chromium for Slackware (contd.)

It’s been ‘fun’ compiling the newest Cheomium 143 sources… as usual when Google updates the major version number.
Again, it is momentarily not possible to compile the Chromium sources using Slackware’s own compilers. I get a Rust error “error: extern blocks must be unsafe” in compiling ‘liballoc_error_handler_impl_ffi.rlib‘. which I have been unable to fix – my knowledge of the Rust programming language is non-existent.
Which is why I could only upload the 64bit packages for chromium and chromium-ungoogled; Google only offers a 64bit version of the heavily patched clang and rust compilers they use internally to compile Chrome. A 32bit package will only become available after I found a fix for the Rust error.
Also, I had to apply some hacks in order to deal with the need for a newer Python than the 3.9 which is part of Slackware 15.0. I already have a successful patch for another part of the code where Python 3.9 was too old (the pipe union operator ‘|’ was added in Python 3.10) but due to time constraints I could not examine the new code and instead added a Python 3.12 binary in parallel.

This means you currently cannot simply run the SlackBuild on Slackware 15.0; you have to add a Python 3.12 package (I compiled a package from the sources I took from from Slackware-current) and point the ‘/usr/bin/python‘ symlink to python3.12. I hope to have fixed that requirement in the next batch of chromium packages.

© 2026 Alien Pastures

Theme by Anders NorenUp ↑