KaOS Linux 2025.07 arrives as a landmark release that draws a hard line: Qt5 is gone. The independent, rolling distribution has completed its transition to a Qt6‑only world, shipping with KDE Plasma 6.4.3 atop Qt 6.9.1 and the Linux 6.15 kernel. For users who value a tightly curated, desktop‑first experience, the July 2025 snapshot delivers a coherent stack where every layer—from the login manager to the audio server—moves in lockstep.

A snapshot that sets a new baseline

KaOS 2025.07 uses the predictable ISO refresh naming and pushes the project’s baseline forward aggressively. The headline numbers: Plasma 6.4.3, KDE Gear 25.04.3, KDE Frameworks 6.16, and Qt 6.9.1 form a unified desktop environment. Underneath, Linux 6.15 brings incremental but meaningful improvements to graphics, storage, and power management. The full roster includes Mesa 25.1.6 for graphics, PipeWire 1.4.6 for audio/video routing, CMake 4.0 for builds, systemd 254.27, OpenSSL 3.5.1, cURL 8.15.0, and OpenZFS 2.3.2—a comprehensive update that touches every subsystem.

This release marks the point where Qt5 removal is no longer a future goal but a day‑to‑day reality. The repositories no longer carry Qt5 libraries, plugins, or theme assets. Applications that have not been ported to Qt6 are absent unless forward‑ported. In their place, new Qt6 ports appear out of the box: the Amarok music player returns, and plasma‑keyboard provides on‑screen input. A Plasma‑native login manager also lands in the repos, signaling a future move away from SDDM.

The philosophy of intentional scope

KaOS remains a study in constraint. It ships a single desktop—KDE Plasma—and a single toolkit—Qt. This narrow focus eliminates redundant settings panels, theme mismatches, and cross‑toolkit edge cases. The trade‑off is a smaller official repository and a sharper expectation of what gets included. Independence is equally important: KaOS uses pacman but maintains its own repositories, built and patched for KaOS goals, with no AUR access. Community contributions flow through KaOS‑specific channels, and the project curates everything to protect stack coherence.

This design attracts users who want a stable, consistent Plasma experience without carrying legacy compatibility layers. It suits modern hardware where keeping a focused set of applications current matters more than accessing tens of thousands of optional packages.

Plasma 6.4.3 and Qt 6.9.1: a coordinated desktop

Plasma 6 consolidated the Wayland transition and refined window management. The 6.4.3 release continues with stability fixes and polish passes that reduce update friction. Wayland is the default, with improvements in compositing, fractional scaling, touch input, and high‑DPI behavior. System Settings panels are cleaner and better reflect real‑world workflows. Discover, the software center, gets incremental updates for update visibility and error messaging—important on a curated distro. KWin sees stability fixes for latency, tearing, and multi‑monitor/hybrid GPU setups.

Qt 6.9.1, the foundation for Plasma and most KaOS applications, is more than a version bump. It brings performance gains in rendering and input handling, broader C++20/23 support, and refinements that keep large applications responsive. Standardizing on a single toolkit yields cumulative improvements in startup times, theme fidelity, and font rendering consistency across the entire desktop.

Cutting the Qt5 cord: why it matters

Dropping Qt5 removes an entire parallel universe of libraries, plugins, and theme assets. The benefits are immediate: a smaller security surface, unified theming and widget behavior, better memory locality, and fewer duplicate resident libraries. No more mismatches between Qt5 and Qt6 style engines or icon handling.

The trade‑offs are real: legacy apps not ported to Qt6 disappear from the repos. Niche utilities may be missing until alternatives or sandboxed packaging fills the gap. KaOS embraces this constraint intentionally, accelerating the KDE ecosystem’s migration within its borders. New applications like plasma‑keyboard and Amarok demonstrate the payoff of focusing development effort on Qt6 ports.

plasma‑login‑manager: a Plasma‑native front door

SDDM has long been the default display manager in KDE‑centric distros. KaOS 2025.07 introduces plasma‑login‑manager in the repositories as an eventual replacement. Written with the same technologies as the desktop, it promises more consistent theming, better Wayland alignment, and fewer dependencies—no need to pull in non‑Plasma components just to bridge gaps. In this snapshot, plasma‑login‑manager is installable but not yet the default. Expect it to replace SDDM once edge cases like complex keyboard layouts and encrypted root setups are fully vetted.

Linux 6.15: kernel‑level desktop improvements

The jump to Linux 6.15 brings incremental but impactful progress. The DRM subsystem tracks new GPUs with updates across AMD’s amdgpu, Intel’s i915/xe, and open NVIDIA kernel modules. Storage subsystems see continued Btrfs and ZFS (via OpenZFS 2.3.2) interoperability improvements, while ext4 and XFS carry on their reliable cadence. Input fixes for modern touchpads, wireless dongles, and Bluetooth LE devices translate directly into better plug‑and‑play on newer laptops. Power management refinements benefit recent Intel and AMD mobile parts, with scheduler and cpufreq tweaks that improve idle and boost behavior. Audio quirks for UCM profiles and USB interfaces get the usual sprinkling of fixes, critical for PipeWire‑based desktops.

A focused graphics, audio, and media stack

KaOS leans on three subsystems for its desktop experience: Mesa, PipeWire, and GStreamer. Mesa 25.1.6 brings driver stability and performance tweaks for AMD and Intel GPUs, with Vulkan and Gallium‑based OpenGL benefiting from regression fixes. PipeWire 1.4.6 consolidates multi‑client stability, Bluetooth codec handling, and low‑latency behavior, routinely handling screen capture and pro‑audio without JACK/PulseAudio gymnastics. GStreamer 1.26.4 updates codec and demuxer handling, broadens hardware‑accelerated decode paths, and reduces synchronization hiccups in video calls or when juggling USB mics and HDMI audio.

Core toolchain and libraries: incremental but essential

Beyond the desktop, KaOS layers a current toolchain: systemd 254.27 for predictable boot and service management, OpenSSL 3.5.1 for cryptography, Protobuf 31.0 and SQLite 3.50.3 for serialization and embedded databases, Glib2 2.84.3 for event loop consistency, IWD 3.9 and cURL 8.15.0 for wireless and HTTPS primitives, and tzdata 2025b for timezone correctness. Perl 5.40.2, GNU Bash 5.3, and Shadow 4.18.0 handle system scripting and user management. CMake 4.0 signals evolved defaults and better package find modules, easing native Qt/KDE development.

Installation and the rolling update path

KaOS targets modern 64‑bit UEFI systems and ships a polished live environment with the Calamares graphical installer. The ISO serves as both an installer and a recovery/update launchpad. For existing systems, the rolling update model applies: refresh keyrings, synchronize databases, and perform a full system upgrade. The project recommends a clean snapshot install only when repaving a system or recovering from a configuration that no longer aligns with repository assumptions—an edge case. The separation of snapshot ISOs from the rolling repository stream allows a coherent, testable starting point while keeping daily drivers on the fast‑moving Plasma and kernel tracks.

Software availability and curation strategy

KaOS carries the KDE/Qt stack in depth but chooses coverage over count for the rest. The result is a surprisingly complete set of core packages for daily work—browsers, office tools with Qt integration, terminals, editors, and utilities—without the redundancy of larger distros. Overlap is reduced: multiple GTK apps that duplicate KDE tools are generally excluded unless a clear functional gap exists. Quality is emphasized through consistent toolchain and Plasma‑environment testing. The Qt6 pivot demonstrates a willingness to break compatibility when the net benefit is clear, but migration windows and alternative paths are typically provided. Flatpak support is available but native packaging remains the preference for performance and integration.

Drivers, firmware, and hardware support

Kernel and Mesa updates carry most of the load for new hardware, but KaOS also addresses UEFI quirks, NVMe controller peculiarities, and wireless firmware rows. IWD and NetworkManager cooperation is a specific focus, as is ensuring Bluetooth LE audio and HID devices appear with the right profiles. OpenZFS availability boosts power users who rely on snapshots and checksumming. Ext4 remains the default for simplicity, while Btrfs continues to improve with subvolume and compression features. On the graphics side, Mesa 25.1.6 and Linux 6.15 promise better out‑of‑the‑box support for recent GPUs and less babysitting for hybrid graphics laptops, with Plasma’s Wayland session benefiting from closing gaps in color management and VRR.

Security posture and update discipline

KaOS’s security model starts with a smaller attack surface—fewer packaging formats and parallel toolkits reduce potential entry points. Security advisories for the curated package set are tracked closely, and updates for OpenSSL, cURL, and systemd are pushed quickly. The rolling model ships fixes in situ rather than backporting across large version gaps. The staged rollout of plasma‑login‑manager—available in repos first, then default—reflects a security‑conscious approach that privileges real‑world testing over big‑bang switches, with careful attention to PAM stacks, theming, and accessibility.

Developer experience on KaOS

With Qt 6.9.1, CMake 4.0, and a current Clang/GCC toolchain, KaOS doubles as an efficient development workstation for Plasma‑aligned projects. Predictable headers and libs prevent mismatch issues. Modern C++ workflows are enabled by default. Testing applications within a fully Qt6 Plasma desktop reveals integration flaws early—icon naming, palette usage, high‑DPI scaling—while the minimal GTK/GNOME library set avoids diluting the environment.

Desktop polish and daily usability

Much of KaOS’s value is about what doesn’t happen: no cascading theme changes from legacy Qt5 apps, no cursor theme jumps, no inconsistent font rendering. The entire stack—from SDDM (today) to plasma‑login‑manager (tomorrow), from KWin to Discover—shares the same design language and toolkit. Daily workflows benefit from reliable suspend/resume on laptops, sound device sanity via PipeWire and ALSA UCM profiles, and improved fractional scaling and multi‑monitor competency under Wayland. Defaults are restrained; only a small set of preinstalled KDE applications are present, leaving office suites and creative tools a few clicks away.

Comparisons and positioning

Against KDE neon, KaOS pushes currency across the entire stack rather than just the desktop. Against Fedora KDE Spin/Kinoite, it trades repository breadth for a coherent Qt‑only experience. Against Arch with Plasma, it borrows pacman ergonomics but enforces KDE/Qt focus with its own repos. Against openSUSE Tumbleweed/Krypton, it hews to a single desktop paradigm, minimizing variability. KaOS’s value stands out when the goal is a current Plasma desktop on a distribution that rarely asks the user to mediate between divergent stacks.

Gaming, graphics APIs, and performance

Gaming on KaOS benefits from the same advances that lift all modern Linux gaming: current kernels, fast‑moving Mesa Vulkan drivers (25.1.6 optimizes shader cache and pipeline compilation), and Proton/Wine improvements. The focus on contemporary GPUs and Wayland compositing can aid frame pacing and HDR pipeline work, though specialized gaming setups may tweak compositor settings. KaOS provides the graphics and audio bedrock and expects specialized layers to be added selectively, keeping the base image light.

Internationalization, input, and accessibility

plasma‑keyboard and the Qt6 input method framework narrow gaps in virtual keyboard and complex script support under Wayland. KDE language packs inherit improved panel and applet translations. Accessibility tooling benefits from evolving screen reader hooks and high‑contrast themes, and the move to a Plasma‑native login manager should yield better continuity from greeter to desktop.

The case for KaOS 2025.07 on modern hardware

New laptop owners and desktop builders looking for a current, KDE‑forward distribution will find KaOS 2025.07 aligned with that brief. The live ISO surfaces quick boot, a clean Plasma session, predictable device detection, and an installer that handles partitioning and encryption without fuss. After installation, the absence of drift is striking—update cycles rarely produce split‑brain scenarios because only one primary desktop stack exists. Breakage is limited and addressed inside the project’s own packaging pipeline. The flip side is selectivity: niche Qt5 or older GNOME/GTK apps may be absent, requiring sandboxed alternatives. But for workflows that thrive in a Qt‑first world, the 2025.07 release provides a clean, current baseline where all the pieces fit.