Today KDE Frameworks 6.22.0 were released, and yesterday we already saw new KDE Gear 25.12.1 tarballs.
Note – in ‘ktown’ you will find that KDE Gear packages are split over ‘kdepim’ and ‘applications’.
I built new packages for those new sources and now you can get the packages for 32bit and 64bit Slackware from the original server: https://slackware.nl/alien-kde/current/testing/ or else from one of its mirrors.
For US folk, this one already has all the new packages: https://us.slackware.nl/alien-kde/current/testing/ .
You can download the sources from https://slackware.nl/alien-kde/source/testing/ and if you want to track the changes in git, go visit https://git.slackware.nl/ktown/log/?h=6_26.01
Have fun! Eric
I’d just like to comment here for exposure, I have a full 1:1 copy of ktown Plasma 6 available for slackware-current aarch64 here:
https://slackware.lngn.net/pub/aarch64/slackwareaarch64-current/ktown/
This repo will be kept up to date with upstream ktown for the foreseeable future.
Great. Thanks!
Btw, the link to “KDE Frameworks 6.22.0” is broken.
Cheers, Marco
Interesting, how did I screw up the copy/paste… in any case it’s fixed now, thanks 🙂
Thanks, Eric!
Is there any way to recreate the Nvidia driver, Wine, and Multilib modules from the live version in the latest folder? Previously, several modules were available, but in the recent update of January 3, 2026, I’m seeing only various ISOs of different versions, but no additional modules. Thank you very much in advance. If it’s not possible, could you give us an idea of ??the steps to create them manually? Happy New Year!
Indeed I removed all the stuff nobody ever asks or talks about. Why spend effort for nothing when time’s short. But I will look at recreating those three modules at least.
For the nvidia and wine modules, the scripts that create them have been part of the liveslak repository forever; see here for instance: https://slackware.nl/slackware-live/liveslak/contrib/scripts/
Creating a multilib module is part of what the ‘make_slackware_live.sh’ script does for you when you tell it to.
Thanks Eric! Applied the updates, and so far everything runs well, no issues.
calligraplan 4.0.1 is ready, this version, is the new port to qt6/kf6, it build without problem here,
https://download.kde.org/stable/calligraplan/calligraplan-4.0.1.tar.xz
I pushed this update to the repository yesterday already…
Vu after 😉
Hi Eric,
Just two cosmetics changes suggestion, for ‘merkuro’ and ‘zanshin’, it are in the ‘pim’ group on ‘invent.kde’ , maybe moved it in kdepim module in place of the module applications.
https://invent.kde.org/pim
You have a point there.
Hi, Eric! It’s nice to see you getting ktown going forward again. Let’s hope it gets integrated into Slackware at some point before you need to pull the plug.
This update brought issues to kmail. When composing a new mail message I see this on console:
> org.kde.pim.pimcommonactivities: Plasma activities is not running: 1
> qt.core.qobject.connect: QObject::connect(KIdentityManagementCore::IdentityActivitiesAbstract, KIdentityManagementCore::IdentityTreeSortProxyModel): invalid nullptr parameter
> qt.core.qobject.connect: QObject::connect(MailTransport::TransportActivitiesAbstract, MailTransport::TransportSortProxyModel): invalid nullptr parameter
> kmail: symbol lookup error: /usr/lib64/libKPim6MessageComposer.so.6: undefined symbol: _ZN17TextAddonsWidgets23RichTextQuickTextFormat14setFormatTypesERK6QFlagsINS0_19QuickTextFormatTypeEE
Is it just me? Should I open a bug issue upstream?
You’re not alone.
The symbol that is missing (_ZN17TextAddonsWidgets23RichTextQuickTextFormat14setFormatTypesERK6QFlagsINS0_19QuickTextFormatTypeEE) is from
/usr/lib64/libKF6TextAddonsWidgets.so.1.8.0, part of the ktextaddons-1.8.0-x86_64-1alien.txz package. The latest version of that package is ktextaddons-1.9.0-x86_64-1alien.txz and that symbol is _ZN17TextAddonsWidgets23RichTextQuickTextFormat14setFormatTypesE6QFlagsINS0_19QuickTextFormatTypeEE. It looks like Eric has to recompile (part of) the PIM package against ktextaddons-1.9.0. As a workaround you can reinstall ktextaddons-1.8.0-x86_64-1alien.txz.
Indeed https://gitlab.archlinux.org/archlinux/packaging/packages/messagelib/-/issues/1 also documents that the ktextaddons update is to blame.
Instead of recompiling all of KDEPIM I will downgrade the ktextaddons package and upgrade it again together with the next KDE Gear release which is scheduled for February 2nd.
Great! ktextaddons downgrade did the trick.
Thanks Sebastian and Eric.
Bug on kio:
https://mail.kde.org/pipermail/distributions/2026-January/001670.html
https://download.kde.org/stable/frameworks/6.22/kio-6.22.1.tar.xz
Yes it’s a bugfix, but if you read the email it actually does not seem safe to update *only* this package.
Just asking: in your upcoming LibreOffice release, and only if this is allowed by the LibreOffice code, would it be possible to release the KDE integration part compiled against Plasma6?
Thanks again!
Nope. There is no Plasma6 in Slackware.
Hello, tried ktown plasma 6 and have to say I’m pretty impressed. everything works as charm except konqueror.
It works, but can’t open settings with immediate segfault
gdb output
Thread 1 “konqueror” received signal SIGSEGV, Segmentation fault.
0x00007fffe93b0b27 in KCoreConfigSkeleton::read() () from /usr/lib64/libKF6ConfigCore.so.6
and it’s backtrace
#0 0x00007fffe93b0b27 in KCoreConfigSkeleton::read() () at /usr/lib64/libKF6ConfigCore.so.6
#1 0x00007fff78261898 in GeneralSettings::self() () at /usr/lib64/libdolphinprivate.so.6
#2 0x00007fffa0018d7f in ??? () at /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so
#3 0x00007fffa0019120 in ??? () at /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so
#4 0x00007fffa0019c2c in ??? () at /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so
#5 0x00007fffa001af3c in ??? () at /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so
#6 0x00007fffa0016dad in ??? () at /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so
#7 0x00007fffa0017bc0 in ??? () at /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so
#8 0x00007ffff7eb77dc in ??? () at /usr/lib64/libKF6KCMUtils.so.6
#9 0x00007ffff7eb6c73 in KCModuleLoader::loadModule(KPluginMetaData const&, QWidget*, QList const&, std::shared_ptr const&) () at /usr/lib64/libKF6KCMUtils.so.6
#10 0x00007ffff7ebcdc2 in KCMultiDialog::addModule(KPluginMetaData const&, QList const&) () at /usr/lib64/libKF6KCMUtils.so.6
#11 0x0000000000507fef in ??? ()
#12 0x00000000004aaa82 in ??? ()
#13 0x00007fffe75c0c36 in ??? () at /usr/lib64/libQt6Core.so.6
#14 0x00007fffe8233120 in QAction::activate(QAction::ActionEvent) () at /usr/lib64/libQt6Gui.so.6
#15 0x00007fffe75ba772 in QObject::event(QEvent*) () at /usr/lib64/libQt6Core.so.6
#16 0x00007fffe88f9238 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt6Widgets.so.6
#17 0x00007fffe754a898 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt6Core.so.6
#18 0x00007fffe754e46e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt6Core.so.6
#19 0x00007fffe78db417 in ??? () at /usr/lib64/libQt6Core.so.6
#20 0x00007fffe656fb16 in ??? () at /usr/lib64/libglib-2.0.so.0
#21 0x00007fffe6572c1f in ??? () at /usr/lib64/libglib-2.0.so.0
#22 0x00007fffe657334c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#23 0x00007fffe78db5b8 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt6Core.so.6
#24 0x00007fffe7559296 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt6Core.so.6
#25 0x00007fffe75531ac in QCoreApplication::exec() () at /usr/lib64/libQt6Core.so.6
#26 0x0000000000462d59 in ??? ()
#27 0x00000000004635e2 in ??? ()
#28 0x000000000044a398 in ??? ()
#29 0x00007fffe6a2ad14 in __libc_start_call_main () at /lib64/libc.so.6
#30 0x00007fffe6a2adc6 in __libc_start_main_impl () at /lib64/libc.so.6
#31 0x000000000044a4f1 in ??? ()
does anybody experience the same? tried several things even based on AI advices kreting some symlinks manually, but no luck.
got it work now. the only trick was
mv /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so /usr/lib64/qt6/plugins/dolphin/kcms/kcm_dolphinviewmodes.so.disabled
may check with next update it still requires kcm_dolphinviewmodes.so disabled or not
anyway, found no issue to the entire desktop system
Hi Ivan, I will try to remember that workaround. I cannot explain why this worked and I also can not find any other report online of a similar crash in konqueror.
Another fix:
https://mail.kde.org/pipermail/distributions/2026-January/001671.html
Indeed, but it is not a critical bug and only affects corner cases. Considering workload I’ll probably wait two weeks for the Plasma 6.6 source tarballs, the fix has already been applied to the master branch.
Hi Eric
Thanks to you and others for picking up KDE/Plasma 6. It’s working really well here but 2 notes:
1. your VLC 3.0.23 package from KTown panics when trying to cast (to my chromecast); your 3.0.21 package from the restricted sbrepo works fine
2. when using a slideshow for wallpaper type in screen locking, the images will initially show on screen lock, but after about 2 minutes the screen just goes black – moving the mouse brings the current wallpaper back along with the password prompt
Thanks for all your work on KTown – there’s many that appreciate it.
Regards, Robby
In the Power Management section of System settings you can set “Turn off screen when locked” to a higher value. You could set “turn of screen” to “never” but you cannot do that independently for the locked screen.
Regarding VLC, “panicking” is not really a bug report, right?
What do you do *exactly* and what is VLC’s behaviour, including the error output on the commandline?
Note that the VLC I added to Slackware Ktown is a lot slimmer than the ones I provide in my own repositories. Could be that it simply lacks the casting capability now, but show me the errors first.