Fedora 42 kills X11 and puts DNF5 in charge — here’s your RHEL 10 preview

Fedora 42, released on April 14, 2026, draws a clean line under two decades of Linux desktop history. The X11 session is gone from the default Workstation install, and DNF5 takes over as the one package manager that ships. The kernel bumps to 6.15, GNOME 48 polishes the desktop experience, and systemd 257 keeps consolidating. These aren’t cosmetic choices — they’re the blueprint for what Red Hat Enterprise Linux 10 will impose on enterprise fleets in eighteen to twenty-four months. Here’s the roadmap.

DNF5 — more than a spring clean

This is the most visible change for anyone who types dnf install a dozen times a day. DNF5 replaces the old DNF (which itself replaced Yum) with a unified C++ codebase, significantly faster dependency resolution, and a memory footprint roughly 40% smaller than DNF4.

Three improvements change the daily admin workflow. First, automatic PGP key management: DNF5 detects and removes expired repository keys without manual intervention — a recurring annoyance on systems that don’t get patched weekly. Second, optional Copy-on-Write support speeds up installations by avoiding redundant file copies during RPM transactions. Third, the git package is now split into git-core for systems that only need the base binary without the full suite — a welcome dependency trim for container images and minimal servers.

For teams with automated deployments, the CLI syntax stays compatible with classic dnf. Ansible playbooks and CI/CD pipelines that call dnf install keep working without modification. Under the hood, however, the speedup is real: on a dnf update with 2,000 packages to sync, DNF5 finishes roughly 35% faster than DNF4, per benchmarks published by the Fedora team.

X11 removed — a Wayland-only future

This is the headline that will echo loudest through IT departments. Fedora 42 removes the GNOME X11 packages from the default installation image. The “GNOME on Xorg” session no longer exists. Users upgrading from Fedora 41 are transparently switched to the Wayland session.

The groundwork was laid years ago. Fedora 36 made Wayland the default, including for NVIDIA cards. Fedora 41 dropped the X11 session from installation media. Fedora 42 takes the final step by removing the packages themselves.

Legacy X11 applications aren’t abandoned: XWayland continues to handle them transparently. Flatpak-packaged software, terminals, IDEs, and modern browsers have run natively under Wayland for several releases now. The remaining friction points involve screen capture and screen sharing tools that relied directly on the X11 API: OBS Studio, RDP clients, and some telemedicine software must migrate to PipeWire and the xdg-desktop-portal protocol — a migration that is already complete for nearly all of them by 2026.

For fleet administrators, the message is straightforward: if your workstations still run X11 out of necessity (unported line-of-business software, exotic GPU), stay on RHEL 9 through its end-of-maintenance in 2032. But don’t expect RHEL 10 to extend X11’s lifespan.

GNOME 48 — triple buffering and digital wellbeing

The GNOME 48 desktop ships three improvements that matter, beyond the cosmetic novelty factor.

Dynamic triple buffering is the most impactful day-to-day change. After over five years of development and testing, this feature reduces frame drops and smooths animations, particularly on integrated-GPU machines and multi-monitor setups. The desktop no longer stutters when resizing a window or scrolling a heavy page.

The digital wellbeing feature introduces screen time tracking, break reminders, and the ability to schedule downtime windows. It’s a direct borrow from mobile interfaces and a signal that GNOME now sees itself as a full operating system rather than just a window manager.

Finally, notification stacking groups messages by application. No more overflowing notification panels after an hour of CI builds: Slack alerts, Git notifications, and system popups are now stacked and scannable.

Under the hood — kernel 6.15, GCC 15, and containers

Fedora 42’s backbone rests on the Linux 6.15 kernel, which enables AMD SEV-SNP confidential VM support by default and introduces the Intel SGX software stack for trusted execution environments. Both features directly benefit teams deploying sensitive workloads in the cloud or on shared infrastructure.

The compiler suite moves to GCC 15 with improved C23 support, joined by LLVM/Clang 20. On the language side, Go 1.24, Ruby 3.4, and PHP 8.4 ship current. Python 3.8 is fully retired from the repositories — applications must target Python 3.9 minimum, and ideally 3.12 or 3.13 to benefit from interpreter performance gains.

In the container space, Fedora CoreOS switches update delivery from OSTree to standard OCI container registries, aligning the immutable OS with Kubernetes and Podman workflows. Atomic Desktops (Silverblue, Kinoite) enable ComposeFS by default for filesystem composition, improving integrity verification and deduplication. Finally, Fedora now produces official WSL images, making the Fedora/RHEL ecosystem easier to adopt on enterprise Windows workstations.

What RHEL 10 will keep — and what it will drop

The rule is well established: every RHEL release is a stabilized snapshot of a Fedora release, frozen for a decade of maintenance. RHEL 9 (2022) was built on Fedora 34. RHEL 10, expected in late 2027 or early 2028, will almost certainly be built on the foundations laid by Fedora 42 and 43.

Here’s what will almost certainly land in RHEL 10:

• DNF5 as the sole package manager. The transition will be transparent for scripts, but administrators must update troubleshooting procedures — logs and debug options change.
• Wayland by default, X11 absent. Xorg server packages will not ship. XWayland will remain available for X11 client applications. Software that still depends on a full X server must migrate before the cutover.
• A stabilized 6.x LTS kernel, with SEV-SNP and SGX for confidential workloads. RHEL 10 will be the first Enterprise Linux release to offer these features with full support.
• ComposeFS and OCI for Atomic and CoreOS deployments, aligning RHEL with container ecosystem standards.
• GCC 15, Python 3.12+, Go 1.24 in Application Stream channels, with the usual two-to-five-year support window depending on the component.

What RHEL 10 will likely not include:

• KDE Plasma Edition, promoted to full Edition status in Fedora 42: RHEL remains a GNOME/Workstation product; KDE is a community offering.
• COSMIC Desktop (System76’s Rust spin): too young, no enterprise support announced.
• Anaconda Web UI: the web-based installer is still maturing. RHEL will likely keep the classic text-based Anaconda interface for Kickstart deployments, with the Web UI available as an option.

The verdict — what RHEL admins should do right now

If you manage a RHEL 9 fleet today, you have two years to prepare the move to RHEL 10 without rushing. Here’s the priority-sorted action list:

• Audit your X11 dependencies. Identify line-of-business applications that still use a full X server and plan their migration to Wayland or their replacement. The timeline is comfortable, but these migrations routinely take longer than expected — start now.
• Test DNF5 on a Fedora 42 box. Ansible playbooks and build pipelines won’t break, but plugin hooks and output formats change. Verify that your monitoring tools that parse dnf output don’t produce false negatives.
• Build your containers on Fedora bases. fedora:42 images give you an exact preview of what RHEL 10 containers will look like. Test your Dockerfiles and Helm charts against this base now.
• Migrate Python applications to 3.12. Python 3.8 and 3.9 will disappear from RHEL 10 repositories. The reasonable target in 2026 is Python 3.12, supported by the CPython community through 2028.

Fedora 42 isn’t just another release in the project’s six-month cycle: it’s the moment the Red Hat ecosystem ratifies the end of X11 and the maturity of DNF5. RHEL 10 will have no choice but to carry these decisions forward. The smartest thing you can do is get ahead of them.

References

• Announcing Fedora 42, Red Hat Blog, April 14, 2026.
• What’s New in Fedora Workstation 42, Fedora Magazine, April 15, 2026.
• Fedora 42 Change Set, Fedora Project Wiki.
• Changes/WaylandOnlyGNOME, Fedora Project Wiki.
• RHEL 10 plans for Wayland and Xorg server, Red Hat Blog.
• RHEL 10 — What’s New for Sysadmins, mylinux.work.
• Fedora Linux 42 Release Notes, Fedora Docs.
• GNOME 48 Release Notes, GNOME Project.