I rebased my laptop install to bazzite-dx yesterday and for some reason, the stable branch installed a testing image (testing-44.20260802) instead of the latest stable image (stable-44.20260802). I pinned to the latest stable for now but does anyone know why bazzite rebase helper would do this?
Edit: I just checked the release info again since that was last night for me, and it just installed the same image again. Rebasing via rpm-ostree pulls the same image too. I’m gonna rebase back to normal bazzite for now and check to see if this also happened to my desktop I switched a couple weeks ago
Edit 2: Yep, my desktop was also on a test image. I wouldn’t have even thought to check if the test image wasn’t locking up my laptop. Until now bazzite has been so stable for me, now I’m wishing I left my desktop on fedora as a backup in case something like that happens again
Is it not letting you rebase to stable?
rpm-ostree rebase ostree-unverified-registry:ghcr.io/ublue-os/bazzite:stableRebasing to normal Bazzite worked fine, but for some reason rebasing on Bazzite-DX, even when picking a specific stable image, would pull the testing image from the same day every time
Oh, I see. From the bug reports posted, it looks like the -dx image is based on the bazzite deck 44 image for some reason, which isn’t out of testing yet.
If that’s deliberate it’s an odd choice. The new deck 44 image should be updated to stable soon.edit: Further reading indicates it’s based on the deck image so that they don’t have to maintain two different dx versions.