I’m on Bazzite and was able to rollback and boot get to the desktop, but I’m not completely sure where to go from here. I think I need to pin my current deployment before doing anything else? I think sudo ostree admin pin 0 ? (No, it’s 1)

Help is welcome but I’ve barely begun to troubleshoot and I just installed Discord to ask on there. Looking for sympathy I guess?

Edit: phrasing

EDIT2: Not just me, someone on the uBlue Discourse linked to this post, and other people have posted about it on the Bazzite Discord. Roll back and wait, and curious if you’re also on the Nvidia KDE build too. I should probably be helpful and open an issue on GitHub. :/

Edit 3: devs are working on it :)

Final edit: the devs released a working update this afternoon, I just updated and it works. I kinda like this atomic distro thing, at no point in time was my computer unusable. 10/10 experience, still would prefer to avoid future kernel panic at the disco, lol.

  • MalReynolds@slrpnk.net
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 day ago

    You’ll be wanting sudo ostree admin pin 1 seeing as 0 was broken. Double check with rpm-ostree status.

    Proceed to rpm-ostree update, if that does nothing it means 0 is up to date, personally I’d just wait for a new update using the working deployment, but you can blow away 0 and get it again if you’re keen.

    • AlligatorBlizzard@sh.itjust.worksOP
      link
      fedilink
      arrow-up
      2
      ·
      1 day ago

      You’re right, it’s 1. I went ahead and pinned it. I ran rpm-ostree update and it’s still not working, I’ll keep using the working deployment for the weekend and I’ll have more time to troubleshoot Monday and Tuesday.

      At least I understand what the kernel panic message means thanks to the people here.