Upgrade Your Fedora Silverblue to Version 44: A Complete Rebase Guide

Overview

Fedora Silverblue is an immutable desktop operating system built on Fedora Linux. Unlike traditional distributions, Silverblue uses an atomic update model where the entire system image is replaced during an upgrade — a process known as rebasing. This guide walks you through the steps to rebase your Silverblue installation to Fedora Linux 44, covering both graphical and terminal methods, along with safe rollback procedures. Whether you’re a developer embracing container workflows or a daily user seeking a stable rolling environment, this tutorial ensures a smooth transition to the latest release.

Upgrade Your Fedora Silverblue to Version 44: A Complete Rebase Guide — Source: fedoramagazine.org

Prerequisites

Before starting the rebase process, confirm the following:

System Update: Apply all pending updates to your current Fedora version. Run rpm-ostree update or use GNOME Software. Reboot if necessary.
Backup Important Data: While rebasing is safe, backing up personal files to an external drive or cloud storage is always recommended.
Stable Internet Connection: The upgrade image is several hundred megabytes; ensure a reliable connection.
Optional: Pin Current Deployment: If you want to keep your current working version as a fallback in the GRUB menu, you can pin it before rebasing (see Step 3 in the terminal section).

Step-by-Step Instructions

Method 1: Rebasing Using GNOME Software

This graphical method is ideal for users who prefer a point-and-click experience.

Check for the Upgrade: Open GNOME Software and navigate to the Updates screen. You should see a notification that Fedora Linux 44 is available.
Download the New Image: Click the Download button (or Download label). This fetches the new system image in the background and may take several minutes depending on your internet speed.
Install the Upgrade: Once the download completes, the button changes to Restart & Upgrade. Click it. The system prepares the upgrade, automatically reboots, and boots into Fedora 44. No further action is needed.

Note: The entire process is atomic — if anything goes wrong during installation, the system automatically reverts to the previous deployment.

Method 2: Rebasing Using the Terminal

For power users, the terminal offers fine-grained control. All commands assume you have sudo privileges.

Step 1: Verify the Target Branch

Check that the Fedora 44 Silverblue image is available in the remote repository:

$ ostree remote refs fedora

Look for a line like: fedora:fedora/44/x86_64/silverblue. If it doesn’t appear, wait a few hours and try again — the image may still be propagating.

Step 2 (Optional): Pin Current Deployment

Pinning preserves your current deployment in the GRUB menu so you can easily boot back to it. Identify the deployment index (0 for the booted deployment) using rpm-ostree status, then pin it:

# Index 0 is typically the current deployment
$ sudo ostree admin pin 0

To unpin later (e.g., after the upgrade is stable):

$ sudo ostree admin pin --unpin 2

(Replace 2 with the actual index of the pinned deployment from rpm-ostree status.)

Step 3: Perform the Rebase

Execute the rebase command to switch to Fedora 44:

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

This downloads the new image and sets it as the next boot entry. You’ll see output showing progress.

Step 4: Reboot

Restart your system:

$ systemctl reboot

During boot, you should see the GRUB menu briefly. The default entry should be Fedora Linux 44. If the menu doesn’t appear, press ESC (or Shift on some systems) immediately after the BIOS screen.

How to Roll Back

Silverblue makes recovery easy. If the new version fails to boot or you encounter issues:

Boot the Previous Deployment: At the GRUB menu, select the entry labeled with your previous Fedora version (e.g., “Fedora Linux 43”). The system will start with the old image unchanged.
Make the Rollback Permanent: Once booted into the old version, run:

$ rpm-ostree rollback

This sets the old deployment as the default. The new deployment remains available in GRUB for future use if desired.

Common Mistakes

Skipping the Update Step: Rebasing from an outdated system can cause dependency conflicts. Always run rpm-ostree update first.
Missing the GRUB Menu: If you don’t see GRUB, try pressing ESC repeatedly right after the vendor logo disappears. On UEFI systems, some firmware hides the menu by default.
Forgetting to Pin: Without pinning, the old deployment may be automatically removed after a successful upgrade if cleanup policies are active. Pin if you want guaranteed fallback.
Using Wrong Branch Name: Ensure the ref is exactly fedora:fedora/44/x86_64/silverblue. Mistyping silverblue or the version number will fail.
Interrupting the Download: Do not shut down or disconnect the internet while rpm-ostree rebase is downloading. If interrupted, re-run the command; it will resume.

Summary

Rebasing Fedora Silverblue to version 44 is a straightforward process thanks to atomic updates. You can upgrade via GNOME Software for simplicity or the terminal for precise control. Remember to update your current system first, optionally pin your existing deployment, and verify the target branch. If anything goes wrong, booting the previous deployment from GRUB and running rpm-ostree rollback will restore your system instantly. With these steps, you can confidently enjoy the latest features of Fedora 44 on Silverblue.