Fedora Linux 40 Enters Beta Testing

The testing of the Fedora Linux 40 distribution version has begun, marking the transition to the final testing stage where only critical error corrections are allowed. The release is scheduled for April 23 and will cover Fedora Workstation, Fedora Silverblue, Fedora IoT, Fedora Coreos, Fedora Cloud Base, Fedora Onyx, and Live- Tarics, provided in various user environments such as KDE Plasma 5, XFCE, MATE, Cinnamon, LXDE, Phosh, LXQT, Budgie, and Sway. These assemblies are designed for architectures X86_64, Power64, and ARM64 (AARCH64).

Some of the most significant changes in Fedora Linux 40 include:

  • The desktop in Fedora Workstation has been updated ahead of the release of Gnome 46.
  • The KDE desktop environment has been updated with support for KDE 6 using the Wayland protocol. Support for the X11 protocol-based session has been terminated, and the XWayland DDX server is now involved in the Wayland session for launching X11 applications. This decision was influenced by the upcoming obsolescence of the X.org server in RHEL 9 and the support for Wayland in NVIDIA Proprietary Drivers.
  • Atomically updated user distributions from the Fedora project are now grouped under the Atomic Desktops brand. Fedora Silverblue based on Gnome, Fedora Kinoite based on KDE, Fedora Coreos, and Fedora IoT retain their original names. However, new builds like Fedora Sericea and Fedora Onyx are now distributed under Fedora Sway Atomic and Fedora Budgie Atomic.
  • Updated versions of various packages including LLVM 18, GCC 14, Binutils 2.41, Glibc 2.39, GDB 14.1, PHP 8.3, Ruby 3.3, Go 1.22, Java 21, AMD ROCM 6, BOOST 1.83, 389 Directory Server 3.0.0, Podman 5, PostgreSQL 16, TBB (Thread Building Blocks) 2021.8, SQLALCHEMY 2, and KUBERNETES 1.29 have been included in Fedora Linux 40.
  • The NetworkManager configurator now includes a mechanism for detecting IPV4 address conflicts on the network interface by sending a verification ARM package before assigning an address. Additionally, wireless connections are ensured by using a separate permanent MAC address (stable-SSID mode at NetworkManager).
/Reports, release notes, official announcements.