Gnome 44 on SB?

Silverblue is simply amazing! It has worked flawlessly for me since installing it.
I see chatter about Gnome 44 release, so how long after the release would we expect it to be available for Silverblue?

Fedora seems to have Gnome 44 in the upcoming Fedora 38 release. It is available now in the Beta and should also be in the final release that is arriving soon.

2 Likes

It is on fedora silverblue 38 which will be released on next month so it in beta right now if you want to adopt it right now and test it you can.
Follow this

Else you will get the stable update next month once released.

Thanks the the update @computersavvy
I will just be patient, since everything runs fine now.

If you follow the guide linked by @frankjunior you can pin your current image, install and use the new image based on F38 with Gnome 44, and then if you want you can easily rollback to your pinned image.

1 Like

How do I upgrade to Fedora 38? rpm-ostree upgrade and that’s it? When the final version is released, I mean. I don’t want the beta.

$ rpm-ostree rebase fedora:fedora/38/x86_64/silverblue
Once it’s done you can reboot and you have 38 if you what you can rollback to 37 anytime and it will be in beta untill stable released once it is out you will be pushed to stable with updating your system on that day…or after that release date.

1 Like

It all went went until my MEGA failed. It still only boots to 37, even though I pinned 38 and rebased it as directed.

error: Updating rpm-md repo ‘MEGAsync’: Failed to download gpg key for repo ‘MEGAsync’: Status code: 404 for https://mega.nz/linux/repo/Fedora_38/repodata/repomd.xml.key (IP: 31.216.145.5)

it looks like MEGA is not ready for F38

Can anyone tell me how to get the newly rebased 38 Silverblue to boot?

you can ask mega about that else you can delete that repo and install it from flathub Flathub—An app store and build service for Linux

1 Like

Deleting MEGA and reinstalling the Flathub solves part of the problem.

I followed the instructions to rebase to 38 and it still boots to 37 as per my post.
How do I troubleshoot that?

Yes see when your system is booting you can stop it with esc and then look for what are ostree base images you can see if you can see 38 silverblue just boot into that then you can fix it Admin pin 0.