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