How to rebase to Fedora Silverblue 39 Beta

Originally published at:

Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. Let’s see the steps to upgrade to the newly released Fedora 39 Beta, and how to revert if anything unforeseen happens.

Before attempting an upgrade to the Fedora 39 Beta, apply any pending upgrades.

Updating using terminal

Because the Fedora 39 Beta is not available in GNOME Software, the whole upgrade must be done through a terminal.

First, check if the 39 branch is available, which should be true now:

$ ostree remote refs fedora

You should see the following line in the output:


If you want to pin the current deployment (this deployment will stay as option in GRUB until you remove it), you can do it by running:

# 0 is entry position in rpm-ostree status
$ sudo ostree admin pin 0

To remove the pinned deployment use following command (2 corresponds to the entry position in rpm-ostree status):

$ sudo ostree admin pin --unpin 2

Next, rebase your system to the Fedora 39 branch.

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

Finally, the last thing to do is restart your computer and boot to Fedora Silverblue 39 Beta.

How to revert

If anything bad happens — for instance, if you can’t boot to Fedora Silverblue 39 Beta at all — it’s easy to go back. Pick the previous entry in the GRUB boot menu (you need to press ESC during boot sequence to see the GRUB menu in newer versions of Fedora Silverblue), and your system will start in its previous state. To make this change permanent, use the following command:

$ rpm-ostree rollback

That’s it. Now you know how to rebase to Fedora Silverblue 39 Beta and back. So why not do it today?


Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.

Question: Can I skip versions during rebase of Fedora? For example from Fedora 36 Silverblue to Fedora 38 Silverblue?

Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (37->38 for example) to avoid unnecessary errors.

Question: I have rpm-fusion layered and I got errors during rebase. How should I do the rebase?

Answer: If you have rpm-fusion layered on your Silverblue installation, you should do the following before rebase:

rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release

After doing this you can follow the guide in this blog post.


I did this the other day. As I had intel laptop Lenovo Carbon X1 6th gen, I had to remove discontinued intel drivers:


That is no longer in rpmfusion. I did not need to have uninstall/install for rpmfusion though.

Let’s add a FAQ entry for the next iteration of this post that says that it also applies to Kinoite, Sericea and Onyx.


I always check the comments for previous ones, so it will be in the next one I’ll write. :slight_smile:

1 Like