i would recommend doing that process through a root prompt though due to you messing with your shell
i would recommend doing that process through a root prompt though due to you messing with your shell and homedir
DI typed
sudo su
Hyeah
Hjust double check everything you type in while on root prompt
Hand exit as soon as youre done
Agood idea to set a root passwd too
Awith passwd in the root shell
Aso you dont get locked out in any case
TLooks like Dor filed a freeze exception to get VRR into Gnome 46, that's awesome
Dthree two one here I go
VAfter a restart, the system performed some updates and then hung late into the boot process. After waiting about five minutes, I restarted and tried again, and now I am unable to even alt tab from the Plymouth boot screen, so I am unable to even view what is taking place
VNormally, I can press alt tab to hide it
VThis is getting pretty dire
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
