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

  • ItsPlasmaSir@lemmy.mlOP
    1·
    8 hours ago

    Thanks for the links, I still hadn’t rebased my desktop yet so I took a before and after of both rpm-ostree and fastfetch, and saw 209 in effect

    Before

    After

    What has me still confused is that the different bazzite update tool in the testing image was also confused by the image

    Bazzite Update Tool

    I mean why would it say a stable image has a testing id and bootloader if its not testing