Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
KDE Linux, the upcoming operating system being developed by the KDE project, received a series of important updates throughout May, including improvements to infrastructure, security, testing workflows, and software management. These changes continue to move the project toward a more streamlined and tightly controlled operating system environment.
Although KDE Linux relies on Arch Linux packages for many low-level components, the project is not intended to be a conventional Arch-based distribution. Instead, it is designed as an immutable, image-based operating system focused specifically on KDE technologies, with applications primarily delivered through Flatpak.
One of the major technical changes involves how KDE software is built. Previously, KDE Linux created Arch packages and deployed them using mkosi, a utility used to build complete Linux system images. The project has now transitioned to KDE’s own kde-builder tool, allowing KDE applications and components to be compiled directly without relying on package generation.
Automated testing has also improved significantly. KDE Linux now performs basic boot verification checks to confirm that newly generated images successfully load into the desktop environment. Developers are additionally working on integrating an OpenQA-powered testing framework that will automatically detect broken builds before release and expand automated validation over time.
Kernel-related changes are included as well. KDE Linux is moving away from the Zen kernel a Linux kernel variant optimized for desktop responsiveness and returning to the standard upstream Linux kernel. According to the developers, the Zen kernel did not provide substantial advantages beyond tweaks already integrated into KDE Linux itself.
The distribution has also removed the external OpenRazer and APFS kernel modules. The development team explained that these out-of-tree modules could create complications during Secure Boot verification. APFS functionality will still remain accessible through a FUSE-based implementation, although the current userspace solution may eventually be phased out.
Another notable change is the removal of fuse2, which KDE Linux considers outdated and potentially insecure. As a consequence, older AppImage applications that still depend on fuse2 may no longer function correctly and will need to migrate to fuse3 compatibility.
KDE Linux has also dropped its dependency on the Arch User Repository (AUR). Previously, the project used scripts that pulled software from the AUR and generated PKGBUILD files automatically. Developers determined that this approach introduced concerns related to security, reliability, and long-term maintenance, while also conflicting with the project’s objective of reducing dependence on Arch-specific infrastructure.
Application management has also been refined. KDE Linux now includes a service capable of automatically deploying newly added preinstalled Flatpak applications to existing installations while respecting applications users have intentionally removed.
Additional updates include support for installing locally compiled binaries into /opt/local, since /usr/local remains read-only in KDE Linux. Developers also fixed a bug that caused installation issues when two KDE Linux live USB drives were connected to the same system simultaneously.
For additional details, see the announcement.
