Dagreed
VAt the very least, I can boot into the previous OS tree.
VSo my system is still operable, but this is definitely a sign that the current version is bricked
ONot sure if this is the same thing, but I tried installing the current Bazzite-stable on my desktop and it would not get past the initial boot stage.
VVery possible
OI ended up spamming my BIOS and reverting over to my Windows drive. The bazzite on my HTPC seems to be working without issue tho
Kwas there a message about initramfs during this?
VThere was, but only that it was updating it. Took north of 3 minutes or so, got past it, and was talking about GDM and delaying exiting Plymouth or something to that effect when it just never progressed further
VThe most esoteric packages I tried to install to OSTree were things like Dropbear (which was redundant given the toggle in Gnome settings), Neovim, and Fortune-mod.
DI did a reset on my home dir and still sometimes I get the blinking _ when gamescope is being loaded
Hno idea what would be causing it then
DHey what branch are you currently on. I am asking since you don't experince the blinking _ error. This is what my
rpm-ostree status
Klatest/stable
KSame as you
D/etc/modprobe/amdgpu.conf also does not exist
Hits essentially just an inclusion IF you make the file, it not existing is fine
KIf initramfs was building that can take upwards of 10 minutes
VIt had finished though
VDefinitively
KWeird
VI had the output up and in no uncertain terms had it finished that part
KAnd if you boot that image now, what happens?
VThat image hangs permanently, responding to no input that would previously toggle the view hidden by plymouth
KYou can try deleting it and then updating again via ostree
VHow would I go about deleting it?
KPin your current working image with rpm-ostree, then from it try to update again
VForgive me, I'm still new to all these functions of immutable OSes. How do I go about doing that
VIt's probably under
ostree admin if I had to guess, just running top level commandsKrpm-ostree status
KFind the ID of the pin you're booted from
Ksudo ostree admin pin the_id
KThat'll ensure it's preserved
VI'm guessing my current one is the bottom one, solely based on the version being lower
KThe dot signifies that, yea
KSo pin 1
KIntentional, previously it enabled amdgpu for older AMD hardware
KFsync does that now
KNot an issue
Dwhy would some bugs only happen for certain users even though the base image is the same across all users
KWe don't know what your issue is
KSo I am unable to answer that
KNone of us are able to reproduce it
KYou are correct that with the same base image we should all have the exact same experience outside of changeable files
KEspecially on matching hardware
Dwhat would it mean if I reinstall bazzite and the issue still persists?
KNo change to what I said, we don't know. None of us can reproduce it
KThere was another user that had your issue and a reinstall fixed it for them, so it would be quite surprising if it didn't work for you
Dso for you game mode loads with no issue?
KYes, every single time on my htpc, my LCD Steam deck, and my oled steam deck
Dmaybe @j0rge knows more about this
