Budgie Atomic -> F41 update rebases to Silverblue?

Ask Fedora
, , , ,
1

So I have Budgie Atomic installed, was on Fedora 40, and decided to go ahead and make the jump up to Fedora 41. Went to the Updates tab in Gnome Software (which is the default software store for Budgie Atomic, I believe), and clicked the usual Download button for the F41 upgrade. As expected, it prompted me to restart the computer, which I did…and found myself booting into Fedora Silverblue 41 with the Gnome DE.

Thankfully, it was super easy to just pick the previous option in GRUB to return to Budgie on Fedora 40, but I’m mystified why this happened. I’m not sure what’s going on, but shouldn’t it have given me Budgie Atomic 41? Not switched out the DE on me? This seems like a possible bug. Would be happy to run some commands to help diagnose.

1 Like
2

Hi and welcome to :fedora: !

Is rpm-ostree status referencing to fedora:fedora/41/x86_64/silverblue for the new, F41 deployment? If so, this looks like a bug indeed. You could report it in the desktop-specific issue tracker.

In the meantime, you could upgrade to BudgieAtomic 41 from the command line. I am using Silverblue but I suppose the documentation to upgrade Silverblue should apply to Budgie Atomic as well, replacing the keyword silverblue with onyx[1].

To be on the safe side, you could make sure the Budgie Atomic 40 deployment doesn’t get deleted at this stage, and either roll back to it (with rpm-ostree rollback <index-number>), or just pin it (with sudo ostree admin pin <index-number>[2]).

  1. I guess the old name is still being used here, you should be able to confirm that. ↩︎

  2. Replacing <index-number> with the entry number from the bootloader list. The default bootlader entry has index 0. See man page for details. ↩︎

1 Like
3

Lol

(And what @tqcharm wrote)

1 Like
4

Yes, the commandrpm-ostree status now references silverblue instead of onyx.

State: idle
Deployments:
● fedora:fedora/41/x86_64/silverblue
                  Version: 41.20250107.0 (2025-01-07T02:07:34Z)
                   Commit: 324838c4014c42dccd19e16db2379ea03bb15177bb83dfd1945c770c21d50898
             GPGSignature: Valid signature by 466CF2D8B60BC3057AA9453ED0622462E99D6AD1

  fedora:fedora/40/x86_64/onyx
                  Version: 40.20250107.0 (2025-01-07T03:10:52Z)
                   Commit: 30280f35d8ca23210f085aa52b27ea5fe5f9801401a02059a08aded293df2b78
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite:stable
                   Digest: sha256:72ae13c334ed9db3fc0eee5707d94e9d7d669fd413ea90b49043bdf1e55d51f7
                  Version: 41.20250106.3 (2025-01-07T04:23:44Z)
                   Pinned: yes

  fedora:fedora/40/x86_64/onyx
                  Version: 40.20250106.0 (2025-01-06T01:12:53Z)
                   Commit: cd1c976daea46a25595fa7fe3a8b7e783d656547cf4652ac39f7ae7e1ebe15ba
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
                   Pinned: yes

  fedora:fedora/40/x86_64/onyx
                  Version: 40.1.14 (2024-04-14T18:24:32Z)
                   Commit: 95f207edbdd63277dc2693bc775d0c89dd7545380d0ab42a959b839335dc4cb7
             GPGSignature: Valid signature by 115DF9AEF857853EE8445D0A0727707EA15B79CC
                   Pinned: yes

As for pinning the deployment of Budgie Atomic 40, that was the first thing I did after this happened. I was actually trying to update to 41 first just so I could pin it before rebasing to Bazzite. Serves me right I guess for just not doing it on the command line like a “true hacker man”!

Thanks for pointing me in the right direction for bug reporting though, that would have been my next question!

1 Like
5

I have created an issue at the suggested tracker.

2 Likes