Immutable Budgie transmutes into Silverblue upon upgrade to 42

Hello, Oriole here, I came here today after testing something in virtual machine that seems to be a problem. When I installed the fedora 42 update in the software menu that is provided by the immutable budgie/onyx variant of fedora, it did successfully update to fedora 42! Unfortunately, by doing so, it has entirely changed from a Budgie installation to a Gnome installation. I understand some people may consider this a marked improvement, but regardless, it does not seem to be intentional behavior. What should I do, both, to save the installation and keep it on the Desktop Environment of choice, and to help prevent this from happening to other people’s installs? Thank you.

P.S., I made this account specifically because of this problem, and I hope that if anyone has been met this fate on raw hardware the best of luck in solving it! :grinning_face_with_smiling_eyes:

1 Like

This should help you with rollback and pinning: Budgie Atomic -> F41 update rebases to Silverblue?

After rolling back to Budgie and pinning the latest F41 deployment you have of it, in order to rebase to F42, you can run from the terminal: rpm-ostree rebase fedora:fedora/42/x86_64/onyx, or whatever Budgie-related deployment you see after running rpm-ostree status, but with 42 for F42 release.

1 Like

Yep, that worked, I added it as the solution, and after doing a little bit more digging, I found this problem post, Issue #5: F41 update from Gnome Software rebases to Silverblue on Budgie Atomic - project - Pagure.io, which was solved, so I also want to add that for any future updates (in theory) use discover, not gnome-software suite!

Thank you for your swift help.

1 Like