{"id":136390,"date":"2026-03-10T19:29:19","date_gmt":"2026-03-10T19:29:19","guid":{"rendered":"https:\/\/fedoramagazine.org\/?p=43082"},"modified":"2026-03-10T19:29:19","modified_gmt":"2026-03-10T19:29:19","slug":"how-to-rebase-to-fedora-silverblue-44-beta","status":"publish","type":"post","link":"https:\/\/sickgaming.net\/blog\/2026\/03\/10\/how-to-rebase-to-fedora-silverblue-44-beta\/","title":{"rendered":"How to rebase to Fedora Silverblue 44 Beta"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" width=\"300\" height=\"127\" src=\"https:\/\/sickgaming.net\/blog\/wp-content\/uploads\/2026\/03\/how-to-rebase-to-fedora-silverblue-44-beta.jpg\" class=\"webfeedsFeaturedVisual wp-post-image\" alt=\"\" style=\"margin: auto;margin-bottom: 5px;max-width: 100%\" \/><\/p>\n<p><a href=\"https:\/\/docs.fedoraproject.org\/en-US\/fedora-silverblue\/\" target=\"_blank\" rel=\"noreferrer noopener\">Silverblue<\/a>&nbsp;is an operating system for your desktop built on Fedora Linux. It\u2019s excellent for daily use, development, and container-based workflows. It offers&nbsp;<a href=\"https:\/\/fedoramagazine.org\/give-fedora-silverblue-a-test-drive\/\" target=\"_blank\" rel=\"noreferrer noopener\">numerous advantages<\/a>&nbsp;such as being able to roll back in case of any problems. This article provides the steps to rebase to the&nbsp;newly released Fedora Linux 44 Beta, and how to revert if anything unforeseen happens.<\/p>\n<p>NOTE: Before attempting an upgrade to the Fedora Linux 44 Beta, apply any pending upgrades to your current system.<\/p>\n<h2 class=\"wp-block-heading\">Updating using the terminal<\/h2>\n<p>Because Fedora Linux 44 Beta is not available in GNOME Software, the whole process must be done through a terminal.<\/p>\n<p>First, check if the 44 branch is available, which should be true now:<\/p>\n<pre class=\"wp-block-preformatted\">$ ostree remote refs fedora<\/pre>\n<p>You should see the following line in the output:<\/p>\n<pre class=\"wp-block-preformatted\">fedora:fedora\/44\/x86_64\/silverblue<\/pre>\n<p>If you want to pin the current deployment (this deployment will stay as an option in GRUB until you remove it), you can do it by running:<\/p>\n<pre class=\"wp-block-preformatted\"># 0 is entry position in rpm-ostree status<br \/>$ sudo ostree admin pin 0<\/pre>\n<p>To remove the pinned deployment use the following command ( \u201c2\u201d corresponds to the entry position in the output from\u00a0<kbd>rpm-ostree status<\/kbd>\u00a0):<\/p>\n<pre class=\"wp-block-preformatted\">$ sudo ostree admin pin --unpin 2<\/pre>\n<p>Next, rebase your system to the Fedora 44 branch.<\/p>\n<pre class=\"wp-block-preformatted\">$ rpm-ostree rebase fedora:fedora\/44\/x86_64\/silverblue<\/pre>\n<p>The final thing to do is restart your computer and boot to Fedora Silverblue 44 Beta.<\/p>\n<h2 class=\"wp-block-heading\">How to revert<\/h2>\n<p>If anything bad happens \u2014 for instance, if you can\u2019t boot to Fedora Silverblue 44 Beta at all \u2014 it\u2019s 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:<\/p>\n<pre class=\"wp-block-preformatted\">$ rpm-ostree rollback<\/pre>\n<p>That\u2019s it. Now you know how to rebase to Fedora Silverblue 44 Beta and fall back. So why not do it today?<\/p>\n<h2 class=\"wp-block-heading\">Known issues<\/h2>\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/discussion.fedoraproject.org\/t\/pam-lastlog-change-crashing-gdm\/164467\" target=\"_blank\" rel=\"noreferrer noopener\">PAM Lastlog change crashing gdm<\/a><\/li>\n<\/ul>\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n<p>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.<\/p>\n<p><strong>Question: Can I skip versions during rebase of Fedora Linux? For example from Fedora Silverblue 42 to Fedora Silverblue 44?<\/strong><\/p>\n<p>Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (42-&gt;43 for example) to avoid unnecessary errors.<\/p>\n<p><strong>Question: I have&nbsp;<a href=\"https:\/\/rpmfusion.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">rpm-fusion<\/a>&nbsp;layered and I got errors during rebase. How should I do the rebase?<\/strong><\/p>\n<p>Answer: If you have&nbsp;<a href=\"https:\/\/rpmfusion.org\/\" target=\"_blank\" rel=\"noreferrer noopener\">rpm-fusion<\/a>&nbsp;layered on your Silverblue installation, you should do the following before rebase:<\/p>\n<pre class=\"wp-block-preformatted\">rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release<\/pre>\n<p>After doing this you can follow the guide in this article.<\/p>\n<p><strong>Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),\u2026?<\/strong><\/p>\n<p>Yes, you can follow the&nbsp;<em>Updating using the terminal<\/em>&nbsp;part of this guide for every ostree edition of Fedora. Just use the corresponding branch. For example for Kinoite use&nbsp;<kbd>fedora:fedora\/44\/x86_64\/kinoite<\/kbd><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Silverblue&nbsp;is an operating system for your desktop built on Fedora Linux. It\u2019s excellent for daily use, development, and container-based workflows. It offers&nbsp;numerous advantages&nbsp;such as being able to roll back in case of any problems. This article provides the steps to rebase to the&nbsp;newly released Fedora Linux 44 Beta, and how to revert if anything unforeseen [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":136391,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[45,61,46,47],"class_list":["post-136390","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fedora-os","tag-fedora","tag-fedora-project-community","tag-magazine","tag-news"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/136390","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=136390"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/136390\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/136391"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=136390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=136390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=136390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}