In an unexpected move, the systemd-free Nitrux Linux distro has announced discontinuing its NX Desktop and Plasma support, charting a new path focused on simplicity and minimalism and shifting toward a more streamlined, Wayland-centric approach.<\/p>\n\n\n\n
Initially, the development team had explored reimplementing NX Desktop on Plasma 6 via an AppImage bundle. However, ongoing challenges\u2014ranging from stretched developer resources to limited community contributions\u2014have effectively stalled the progress of Maui Shell, the original replacement for NX Desktop.<\/p>\n\n\n\n
The big news:<\/strong> Nitrux has chosen to adopt a streamlined desktop environment, opting for Hyprland<\/a> along with utilities like Waybar<\/a> and Wlogout<\/a>. This is actually pretty exciting because it makes Nitrux the first distribution to rely on Hyprland as the default desktop experience for its users.<\/p>\n\n\n\n In light of this, as of June 10, 2025, NX Desktop components have officially ceased maintenance, and their corresponding repositories are archived on GitHub.<\/p>\n\n\n\n Hyprland, praised for its lightweight and efficient performance on Wayland, becomes the new default environment, marking a clear departure from the previous KDE-based ecosystem.<\/p>\n\n\n\n But surprises are not stopping here. The kernel underpinning Nitrux is also undergoing a significant change. The team is shifting from the Liquorix kernel to Cachy<\/a> due to Cachy’s support for Pressure Stall Information, which is crucial for Waydroid functionality.<\/p>\n\n\n\n Moreover, Nitrux’s display management infrastructure sees a similar evolution. SDDM, previously tied to Plasma-specific UI elements, will be replaced by greetd<\/a>, a minimal and flexible login manager daemon, combined with QtGreet. This switch supports the team’s continued reliance on Qt and QML, complementing the broader architectural shift toward a Wayland-only environment.<\/p>\n\n\n\n Regarding application distribution, the Nitrux team will prioritize their custom-built NX AppHub and AppBox methods, gradually phasing out AppImages dependent on the older FUSE 2 runtime. The transition aims to consolidate application management around a system expressly tailored for Nitrux, enhancing overall compatibility and performance.<\/p>\n\n\n\n Lastly, future goals include transitioning from SquashFS to DwarFS for ISO creation, driven by the superior performance observed in Nitrux’s own AppBox tool. Additionally, expanding support to ARM64 architectures is on the wishlist, acknowledging growing interest and necessity in single-board computing platforms.<\/p>\n\n\n\n