Chimera Linux 20261103 images ship with kernel 7.3, GNOME 51, Plasma 6.8, drop X.org

Chimera Linux has published its 20261103 install image set, the distribution's first refreshed media in approximately twelve months. The release updates core components to kernel 7.3, GNOME 51, and KDE Plasma 6.8, while eliminating the X.org server from all image variants. For live and base installations, NetworkManager replaces iwd as the default networking stack, a change intended to simplify wireless configuration on headless systems and to prepare for the eventual removal of AF_ALG kernel support.

This incremental refresh does not introduce major image-format changes but bundles a full year of accumulated system updates. The maintainers indicated that the extended gap between image releases was unplanned and expressed hope for a shorter cycle going forward. Users running existing Chimera installations can update through the package manager without reinstalling.

What changed in the 20261103 image set

• Kernel and desktop versions: Images are built against Linux kernel 7.3, GNOME 51, and KDE Plasma 6.8, representing a full year of upstream component updates.
• X.org removal: No image variant ships with the X.org server, completing a transition to Wayland-only desktop environments.
• Network stack change: Base images now include NetworkManager instead of iwd, targeting improved wireless configuration on systems without graphical interfaces.
• AF_ALG preparation: The NetworkManager migration is explicitly tied to readiness for removing AF_ALG (kernel crypto API algorithm interface) from the distribution.
• Incremental scope: The images themselves are described as routine; the significance lies in bundling twelve months of system updates into installable media.

Why it matters

Chimera Linux's move to Wayland-only images and its early preparation for AF_ALG removal signals where a musl-based, BSD-influenced distribution sees the Linux platform heading. For administrators and users, the NetworkManager default reduces friction for headless wireless setup but may require migration for those relying on iwd-specific configurations. The twelve-month gap between install media releases highlights the project's small-team resource constraints, even as its rolling package updates kept existing installations current.