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 :)

  • AlligatorBlizzard@sh.itjust.worksOP
    7·
    7 hours ago

    Update: Good (?) news - I just ran into a comment on the Discourse group linking to this post because they’re having the same issue, and several more people posted on the Bazzite Discord.

    I didn’t break it!

  • Guenther_Amanita 🍄@slrpnk.net
    11·
    10 hours ago

    You did everything right. Boot into the image that works, and then apply rpm-ostree rollback. This reverses the broken image and the working one, so you’ll boot into this one the next time you boot up until you change something in the order, e.g. by updating.

    In the meantime, wait a day or so and then update again.

    On what channel are you on? bazzite:latest or bazzite:stable?

    • AlligatorBlizzard@sh.itjust.worksOP
      3·
      10 hours ago

      Thanks for your help. I was planning on waiting a few days because I’ll have more free time on Monday, I’ll try updating again on Monday.

      I’m on stable.

  • RegalPotoo@lemmy.worldEnglish
    11·
    11 hours ago

    init crashed because it couldn’t load a shared library, but init isn’t allowed to be killed so the kernel panicked

  • dudeami0@lemmy.dudeami.win
    5·
    11 hours ago

    Disclaimer: I have no experience with Bazzite. A quick web search shows that it’s a distro based on Fedora Atomic. That being said, if you did everything according to the documentation, this is probably a bug that should be raised with the developers.

    The first line states /init: error while loading shared libraries: libsystemd-core-256.11.1-fc41.so: c. This is basically the issue, for whatever reason the shared library for systemd (which if being used, is basically the backbone to your systems startup) isn’t available. The next place I would look is whatever tool/command you use to upgrade/build your system, this might of spit out an error related to why this library could not be built or why it’s inaccessible on the next boot. If the solution isn’t obvious from those logs, I would report this to the distro developers as a ticket in their bug tracker.

    As to look at the positives, you have discovered the beauty of immutable/atomic distros. You can just go back to the working version instead of cussing at your PC.

    • AlligatorBlizzard@sh.itjust.worksOP
      4·
      10 hours ago

      The developers are active on Discord and I’ll make a post there Monday when I have more time to tinker with it and reply to people, and until then I’ll enjoy the perks of an atomic distro, lol. Thanks for your help and the thorough explanation!

  • MalReynolds@slrpnk.netEnglish
    3·
    11 hours 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
      1·
      10 hours 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.

  • Onno (VK6FLAB)
    2·
    8 hours ago

    I have no idea what Bazzite is.

    The error says that there’s a missing file. If it used to work, but after you updated, upgraded, compiled, installed or something to get a new kernel, it broke.

    I’m guessing that you installed the wrong kernel or didn’t update the initial ramdisk correctly.

    You might be able to boot using the previous kernel, but I’d start with trying to figure out what you did to get here.

    You should be able to boot from the installation media in rescue mode to fix this, but that won’t happen until you know what’s broken.

  • Telorand@reddthat.com
    1·
    12 hours ago

    When you say “boot,” do you mean that your computer started but didn’t start the OS?

    And yes, I believe that’s the correct command to pin an image. It’s either that or 1. As you update, it will eventually become image 3 and just live there until you unpin it.

    • AlligatorBlizzard@sh.itjust.worksOP
      1·
      12 hours ago

      Ostree: 0 caused the kernel panic, but in grub I selected ostree: 1 (I rolled back to a previous update) and was able to get to the desktop like expected. Boot is the wrong term, sorry.

      • Telorand@reddthat.com
        1·
        3 hours ago

        Yeah you’d want to pin whatever image number you’re using. You’re basically saying, “Yeah, #1 is the good one I want to save for later.”

        ETA: the rollback command does two things:

        • Deletes the offending image (usually the one you’re on).
        • Blacklists the upstream build.

        I cannot recall if you will have to rebase back to the upstream build to start getting updates again or not. I think you will, but double check.