Upgrading to Fedora Linux 44 on Silverblue: A Complete Step-by-Step Guide

Overview

Fedora Silverblue is an immutable, atomic desktop operating system built on Fedora Linux. It’s designed for daily use, development, and container-centric workflows, offering advantages like reliable rollbacks and consistent system states. Upgrading to a new major release, such as Fedora Linux 44, is called a rebase because the entire OS image is replaced atomically. This guide walks you through the entire process—from preparing your current system to performing the rebase using either GNOME Software or the terminal, and finally how to roll back if something goes wrong. No previous experience with rebasing is required, but basic terminal familiarity helps.

Upgrading to Fedora Linux 44 on Silverblue: A Complete Step-by-Step Guide — Source: fedoramagazine.org

Prerequisites

Before you begin, ensure you meet the following:

Fedora Silverblue installed (version 43 or earlier). The procedure is similar for all Fedora Atomic Desktops (like Kinoite, Sericea, etc.), but this guide focuses on Silverblue.
Stable internet connection – the rebase downloads a new image (several hundred MB to a few GB).
Sufficient disk space – at least 10 GB free for the new deployment plus rollback space.
Back up important data – while rebasing is safe, having a backup is always wise.
System updates applied (see next section).

Step 1: Update Your Current System

Always start with a fully updated system to avoid conflicts. There are two methods:

Using Terminal

Open a terminal and run:

rpm-ostree update

This applies pending updates atomically. After completion, reboot.

Using GNOME Software

Open GNOME Software, go to Updates, and install any pending updates. Restart when prompted.

Rebooting ensures your current deployment is clean and ready for the rebase.

Step 2a: Rebase Using GNOME Software (GUI Method)

This is the simplest method for most users.

Open GNOME Software.
Navigate to the Updates screen. You should see a banner or notification that Fedora Linux 44 is available.
Click Download to fetch the new image. This may take several minutes.
Once downloaded, the button changes to Restart & Upgrade. Click it.
The system will prepare the upgrade, reboot, and boot into Fedora Linux 44 automatically.

That’s it! After rebooting, you’re on the new release.

Step 2b: Rebase Using Terminal (Advanced Method)

If you prefer command-line control, follow these steps.

Verify the New Branch Is Available

Check the available remote references for your system:

ostree remote refs fedora

Look for a line like:

fedora:fedora/44/x86_64/silverblue

If you see it, the rebase target is ready. If not, run rpm-ostree update first to refresh the remote metadata.

Pin Your Current Deployment (Optional but Recommended)

Pinning keeps your current system as a bootable entry in GRUB, even after the rebase. This is useful for easy rollback without GRUB menu hunting.

sudo ostree admin pin 0

The 0 refers to the position of your current deployment (check with rpm-ostree status). To later unpin, use sudo ostree admin pin --unpin 2 (adjust the number).

Perform the Rebase

rpm-ostree rebase fedora:fedora/44/x86_64/silverblue

This command downloads the new image and creates a new deployment. It does not apply it until reboot.

Reboot

systemctl reboot

At the GRUB menu, the new Fedora 44 entry will be selected by default. If you pinned, the old entry remains available.

Step 3: How to Roll Back (if needed)

If you encounter boot failures, software incompatibility, or simply change your mind, rolling back is straightforward.

Method 1: Using GRUB at Boot

During boot, press Esc (or Shift on some systems) to enter the GRUB menu.
Select the older deployment (e.g., Fedora Linux 43).
Boot into it. Your system will run the previous version.

Method 2: Make Rollback Permanent

Once booted into the older version, run:

rpm-ostree rollback

This sets the older deployment as the default. You can later rebase again if desired.

Common Mistakes and Troubleshooting

Skipping updates before rebase – This can cause dependency conflicts. Always run rpm-ostree update first.
Network interruption during download – If the download fails, run the rebase command again; it resumes where it left off.
Insufficient disk space – The rebase requires extra room. Free up space or extend storage before retrying.
Unpinned deployments lost – If you didn’t pin and reboot, the old deployment may be garbage‑collected. Use rpm-ostree status to check.
GRUB menu not appearing – Try holding Esc or Shift immediately after the firmware logo. If that fails, you can set a timeout in /etc/default/grub (but that’s beyond this guide).

Summary

Rebasing to Fedora Linux 44 on Silverblue is a safe, atomic process. You can use GNOME Software for a guided experience or the terminal for more control. Always update first, consider pinning your current deployment, and remember that rollback is just a GRUB selection away. With these steps, you can confidently upgrade to the latest Fedora Atomic Desktop.