My bazzite is dropping into emergency mode when I boot, then when I press enter it loads properly. w
My bazzite is dropping into emergency mode when I boot, then when I press enter it loads properly. what's that about?
Tdid you edit fstab recently?
LID | NAME | STATUS | IMAGE
59b14afb993d | fedora | Up 53 minutes | ghcr.io/ublue-os/fedora-distrobox:latest
59b14afb993d | fedora | Up 53 minutes | ghcr.io/ublue-os/fedora-distrobox:latest
Tor mess around with mounting other drives
KYou have a fedora distrobox, for you now you can remove it, they're made to be blown away as needed
_yes, I set a secondary drive up
Kdistrobox stop fedora
_all I did was mount it though
KDistrobox rm fedora
Tmight have an error in it
Tthis is what happened to me when i was auto-mounting my secondary drive with fstab
KIf you changed fstab, your changes are no good
LError: cannot remove container 59b14afb993d213a6ffdbb9560f85ba19a9528f0f2316ab1b841a5272b0ff6f5 as it is running - running or paused containers cannot be removed without force: container state improper
_uh, for somebody who has never edited the fstab file directly, how would I go about undoing the changes?
Tremove the changes you made
Tsave it
Li did use the stop command first, it returned an error too
LError: container 59b14afb993d213a6ffdbb9560f85ba19a9528f0f2316ab1b841a5272b0ff6f5 has active exec sessions, refusing to clean up: container state improper
_the only change I did was mount the drive
Tyeah undo that
_won't that mean I have to mount it manually on each boot?
Ti have an alternative method
Twhat DE do you use?
TKDE or GNOME?
_kde
_I've used gnome disk utility to mount drives in the past, should I use that?
Tyeah i was just going to recommend that lol
TKDE has their own too
Tbut it's not as simplified as GNOME's disk
Tlayer it, reboot
_yeah, I used the KDE one
Tautomount the drive
Tand it should be good
Tobviously undo your changes from before
_ok, I'll do that instead
Tpodman stop 59b14afb993d213a6ffdbb9560f85ba19a9528f0f2316ab1b841a5272b0ff6f5maybe
_in case anybody was wondering, I did manage to get the fan curve problems I was having solved. installed Nobara like somebody suggested, used LenovoLegionLinux to set curves, then switched back to Bazzite because Nobara didn't want to let Squad run
Lthat seems to have stopped it but i still can't rm it
LSo im guessing no one knows what is going on with the issue im having 
_which makes me wonder if running windows in a vm would allow me to use the lenovo tools to set fan curves
KYou can
distrobox rm fedora --forcefedora restarted again by itself
Lmlupo@fedora /v/h/mlupo [2]> distrobox list
ID | NAME | STATUS | IMAGE
59b14afb993d | fedora | Up 48 seconds | ghcr.io/ublue-os/fedora-distrobox:latest
ID | NAME | STATUS | IMAGE
59b14afb993d | fedora | Up 48 seconds | ghcr.io/ublue-os/fedora-distrobox:latest
Lwhy did it restarted itself?
Lforcing seems to have worked
Llist is empty now
KGlad to hear it, there's a patch for the DeckHD in testing as well
KMakes gamescope handle it properly
VOh by the way, the plymouth theme's rotation is still wrong
Lnow i'll see if the ublue updater works
