Fedora 42 Released: New Features, Upgrades, and What Every Linux User Should Know

Fedora has long held a special place in the Linux ecosystem as Red Hat’s upstream innovation laboratory — the distribution where new technologies are proven before making their way into RHEL and, by extension, into enterprise Linux deployments around the world. Fedora 42 continues this tradition with a set of updates that reflect the current state of the art in desktop Linux, developer toolchains, and server-side infrastructure. Whether you run Fedora as your daily driver workstation or as a server testbed, here is a comprehensive look at what Fedora 42 brings to the table.

Release Highlights at a Glance

• Linux kernel 6.14
• GNOME 48
• DNF5 as the default package manager (replacing DNF4)
• Python 3.13
• GCC 15
• LLVM/Clang 19
• Wayland-only by default for new installations
• Improved hardware support for AMD, Intel, and ARM platforms

Linux Kernel 6.14 in Fedora 42

Fedora 42 ships with Linux kernel 6.14, one of the most recent upstream stable kernels. As covered in detail in our kernel 6.14 release article, this brings improved AMD RDNA 4 graphics support, better Intel Lunar Lake power management, Rust subsystem growth, and networking improvements. Fedora users benefit from these improvements out of the box without needing to compile or install a custom kernel.

Fedora’s kernel configuration also includes several patches on top of the upstream stable kernel, including performance and security hardening patches that Red Hat engineers maintain. The combination of a recent upstream kernel with these downstream patches makes Fedora one of the best-supported distributions for new hardware.

GNOME 48: What’s New for Workstation Users

Fedora Workstation is the flagship edition, and it ships with GNOME 48. The headline GNOME 48 features include:

• Improved notification system: GNOME 48 redesigns the notification center with better grouping, clearer dismiss actions, and the ability to interact with notifications directly from the top bar.
• Dynamic triple buffering improvements: The triple buffering patch set that improves animation smoothness on lower-end hardware has been refined further in GNOME 48, providing smoother scrolling and window animations.
• HDR improvements: GNOME 48 extends HDR support to more applications and improves color management when mixing HDR and SDR content.
• Accessibility improvements: The accessibility tree has been refactored to improve performance with screen readers and other assistive technologies.
• Files (Nautilus) updates: The file manager receives improved search performance and a refreshed empty-state design.

DNF5 as the Default Package Manager

This is arguably the most significant under-the-hood change for Fedora 42 users. DNF5 has been available as an optional alternative for several releases, but Fedora 42 makes it the default. DNF5 is a complete rewrite of the DNF package manager in C++, designed to be faster, more memory-efficient, and to offer a better API for tools that interface with the package manager.

For end users, the change is mostly transparent — the commands are the same:

# These commands work identically in DNF4 and DNF5
dnf install package-name
dnf remove package-name
dnf upgrade
dnf search keyword
dnf info package-name

The practical difference you will notice immediately is speed. DNF5 resolves dependencies and downloads package metadata substantially faster than DNF4, particularly on systems with large installed package sets or when updating many packages at once.

# DNF5-specific features
# List installed packages with history
dnf history list

# View what a transaction changed
dnf history info 42

# Undo a transaction
dnf history undo 42

# Clean all cached data
dnf clean all

# Auto-remove unneeded dependencies
dnf autoremove

Python 3.13 and Developer Toolchain Updates

Fedora 42 ships Python 3.13 as the default Python version, bringing several improvements:

• Free-threaded mode (experimental): Python 3.13 includes an experimental build option that removes the Global Interpreter Lock (GIL), allowing true multi-core Python parallelism. Fedora 42 ships the standard GIL build by default, but the free-threaded build is available via python3.13t.
• Improved error messages with more precise location indicators
• A new interactive interpreter with multi-line editing support
• Performance improvements across the board

# Check Python version
python3 --version
# Python 3.13.x

# Install the free-threaded experimental build
dnf install python3.13-freethreaded

# Run with the free-threaded interpreter
python3.13t --version

GCC 15 brings improved C23 standard support, better vectorization for modern CPU architectures including AVX-512 and SVE, and enhanced compile-time diagnostics. LLVM/Clang 19 adds corresponding improvements for the LLVM toolchain ecosystem.

Wayland-Only by Default

Fedora 42 makes a bold but logical move: new installations default to Wayland only, without the Xwayland compatibility layer enabled by default. For users running modern applications — which at this point includes virtually all major Linux desktop applications — this is a non-event. All GTK4, Qt6, and Electron applications run natively on Wayland.

The XWayland compatibility layer is still available and can be enabled for legacy applications that require it:

# Install XWayland if you need it for legacy apps
dnf install xorg-x11-server-Xwayland

# Check if you're running Wayland
echo $WAYLAND_DISPLAY
# Should output: wayland-0

# Check display server type
xdpyinfo | grep -i "X.Org version" || echo "Running Wayland natively"

New Features in Fedora Server Edition

Fedora Server 42 includes several updates of interest to sysadmins:

• Cockpit updated: The Cockpit web-based administration interface receives updates with improved storage management and better network bond/bridge configuration UI.
• Container Tools updated: Podman, Buildah, and Skopeo are updated to their latest versions, with improved rootless container networking and better compatibility with Kubernetes manifests.
• Stratis storage updated: The Stratis storage management system receives performance improvements and better LUKS2 encryption integration.

# Check Cockpit status
sudo systemctl status cockpit

# Enable Cockpit
sudo systemctl enable --now cockpit.socket

# Open Cockpit in browser
# Navigate to https://your-server-ip:9090

New and Notable Packages in Fedora 42

Every Fedora release adds new packages to the repositories. Notable additions in Fedora 42 include:

• OpenTofu (the open source Terraform alternative) is now in the official Fedora repositories
• Updated Podman Desktop for GUI container management
• Go 1.22 as the system Go toolchain
• Rust 1.78 in the default repositories
• Updated Node.js LTS (Node 22)

Upgrading from Fedora 41 to Fedora 42

Fedora makes major version upgrades straightforward using the dnf system-upgrade plugin. The process is reliable and typically takes 20-40 minutes depending on your internet connection and system speed:

# Step 1: Ensure your current system is fully up to date
sudo dnf upgrade --refresh

# Step 2: Install the system upgrade plugin (usually already installed)
sudo dnf install dnf-plugin-system-upgrade

# Step 3: Download the Fedora 42 packages
# This downloads everything needed but doesn't upgrade yet
sudo dnf system-upgrade download --releasever=42

# If you have third-party repos with compatibility issues, add --allowerasing:
sudo dnf system-upgrade download --releasever=42 --allowerasing

# Step 4: Trigger the upgrade on next reboot
# The system will reboot, perform the upgrade in a minimal environment,
# then reboot again into your upgraded Fedora 42 system
sudo dnf system-upgrade reboot

After the upgrade completes and you are booted into Fedora 42, perform some cleanup:

# Remove packages that were installed for the upgrade
sudo dnf system-upgrade clean

# Remove any packages not available in Fedora 42 repos
sudo dnf distro-sync

# Remove old kernels (keeps the 3 most recent by default)
sudo dnf remove --oldinstallonly

# Verify you are running Fedora 42
cat /etc/fedora-release
# Fedora release 42 (Forty Two)

uname -r
# Should show kernel 6.14.x

What Developers and Sysadmins Should Know

For developers, Fedora 42’s Python 3.13 upgrade means checking your applications and virtual environments. Existing virtual environments created under Python 3.12 will continue to work, but you will want to recreate them under Python 3.13 to take advantage of the new features:

# Create a new virtual environment with Python 3.13
python3 -m venv --upgrade-deps ./venv
source ./venv/bin/activate
pip install -r requirements.txt

For sysadmins, the DNF5 transition should be seamless, but any scripts that parse DNF output should be tested since some output format details have changed. Ansible playbooks using the dnf module are unaffected as Ansible’s abstraction handles the version difference transparently.

Fedora 42 is a strong release that delivers meaningful improvements across the desktop, developer toolchain, and server categories. The DNF5 transition and Wayland-default stance are forward-looking decisions that reduce technical debt while offering near-zero disruption for typical users. If you have been running Fedora 41, the upgrade is worth doing soon.

Developer Experience Improvements in Fedora 42

Fedora has always positioned itself as the distribution of choice for developers, and Fedora 42 delivers several improvements specifically for development workflows.

Toolbox and Distrobox Updates

Toolbox (fedora-toolbox) allows running containerized development environments that integrate seamlessly with the host system — sharing the home directory, display, and network. In Fedora 42, Toolbox is updated with improved container lifecycle management:

# Create a Fedora 42 toolbox
toolbox create --image registry.fedoraproject.org/fedora-toolbox:42

# Enter the toolbox
toolbox enter fedora-toolbox-42

# Create a toolbox based on a different distro
toolbox create --distro ubuntu --release 24.04 my-ubuntu-box

# List all toolboxes
toolbox list

# Remove a toolbox
toolbox rm fedora-toolbox-42

Distrobox, the community alternative to Toolbox that supports even more distributions, also benefits from the updated Podman version in Fedora 42:

# Run an Arch Linux environment on Fedora
distrobox create --image archlinux:latest --name arch-dev
distrobox enter arch-dev

# Export an application from a toolbox to the host
distrobox-export --app firefox  # Makes it available in the host's app menu

Podman Desktop for Container Management

Podman Desktop is a GUI application for managing containers, pods, and Kubernetes deployments locally. Fedora 42 ships an updated version with improved Kubernetes emulation via Kind and Minikube integration:

# Install Podman Desktop (Flatpak)
flatpak install flathub io.podman_desktop.PodmanDesktop

# Or install from Fedora repos
sudo dnf install podman-desktop

# Verify Podman version
podman --version
# podman version 5.x.x

Common Fedora 42 Post-Upgrade Issues and Solutions

Even well-tested upgrades occasionally produce minor issues on specific hardware or software configurations. Here are the most commonly reported problems after upgrading to Fedora 42 and how to resolve them:

NVIDIA Driver Compatibility

If you use the proprietary NVIDIA driver from RPM Fusion, it needs to be rebuilt for the new kernel. This usually happens automatically, but if your display does not start after the upgrade:

# Boot to a TTY (Ctrl+Alt+F2)
# Re-install NVIDIA drivers for the new kernel
sudo dnf reinstall akmod-nvidia xorg-x11-drv-nvidia

# Wait for the kmod to build (can take 2-5 minutes)
sudo akmods --force

# Verify the module built
ls /lib/modules/$(uname -r)/extra/nvidia.ko*

# Reboot
sudo systemctl reboot

DNF5 Plugin Compatibility

Third-party DNF plugins written for DNF4 may not work with DNF5. Check for issues with:

# List installed DNF plugins
ls /usr/lib/python3.*/site-packages/dnf-plugins/

# Check for DNF5-incompatible plugins
dnf5 --version
# If you see plugin errors, disable the problematic plugin:
sudo dnf config-manager --set-disabled plugin-name

# Update all packages including plugins
sudo dnf upgrade --refresh

Flatpak Applications After Upgrade

# Update all Flatpak applications after OS upgrade
flatpak update

# If Flatpak runtimes are outdated
flatpak update --system
flatpak update --user

# Remove unused Flatpak runtimes to free space
flatpak uninstall --unused