Akademy 2025, KDE’s yearly developer and community event, this year held in Berlin, Germany. Amid all the various talks and informal meetings, the KDE project also officially unveiled the first alpha release of KDE Linux, a project they’ve been working on for a while now. KDE Linux will serve as a “reference implementation” of KDE Plasma and official KDE applications, for use by developers and regular users alike.
KDE Linux will have a quick update cycle, to ensure its users always have the latest releases of KDE Plasma and various other KDE applications and related technologies. It may, however, not be as optimised as other KDE distributions, and the intent of KDE Linux is not to compete with or replace other distributions. The goal is to show other distributions how KDE itself intends for its software to be presented.
So, what is KDE Linux based on?
KDE Linux is an “immutable base OS” Linux distro with a core created using Arch Linux packages — but it should not be considered part of the Arch family of distributions. Some very fundamental Arch technologies (like the
pacmanpackage manager!) have been removed. KDE software is then built on top of this core using KDE’s homegrown development tools and Flatpak.KDE Linux leans on Systemd for a great deal of functionality. Updates are atomic and image-based, with the last 5 OS images cached on disk for safety. Only the Wayland session is supported. Apps primarily come from Flatpak and Snap.
↫ KDE Linux’ website
The overview of the KDE Linux’ architecture provides some more details. I like that it eschews GRUB in favour of systemd-boot (GRUB should be retired in this, the year of our lord 2025) and relies on systemd-sysupdate for operating system updates. Of note is that the mention of Snap is merely for convenience’s sake as an option; Snap is not a requirement, nor are any Snap packages installed by default.
Since this is the first alpha release, expect bugs and issues, and don’t use it on any production machines until they’re a few more releases in.
Grub is more than a bit unwieldy but its also the most conplete boot manager. Systemdboot is the best option for UEFI but for better or for worse there are many more boot systems than that
Shugo
I really liked syslinux far more than grub, which is too complex and overengineered for my tastes. But the linux community at large really seems to be strongly drawn to more complexity even though IMHO a bootloader should be simple. Syslinux is practically abandoned now, but in it’s prime I experienced way more failure modes with grub due to all the fragile engineering that went into it: struggling with drive mapping and config file sync issues, especially if you had more than one OS or used removable drives. Ultimately all the bugs got fixed for me, but I still don’t like the complexity.
What is this intended to achieve that is not already being achieved by Neon? I do hope that this isn’t a replacement for Neon, which is good and works. I’ve never tried an immutable system i didn’t have to wrestle with.