VGood luck 
Li noticed theres a process keeps showing up in the crashed process viewer: PID: 6952 (sdgyrodsu)
LSignal: 6 (ABRT)
Vsdgyrodsu is a gyroscope server mainly used by emulators, it won't be causing your issue
Lah ok thought maybe since it was in the crashed process might have been something
Jplease don't ping mods
Lsorry wont happen again.
Li tried systemctl status nvidia-powerd.service and it shows me a fail, how could i proceed to fix this?
Ldic 26 18:53:55 fedora /usr/bin/nvidia-powerd[1460]: SBIOS support not found for NVPCF GET_SUPPORTED function
dic 26 18:53:55 fedora /usr/bin/nvidia-powerd[1460]: No matching GPU found
dic 26 18:53:55 fedora /usr/bin/nvidia-powerd[1460]: Failed to initialize RM Client
dic 26 18:53:55 fedora /usr/bin/nvidia-powerd[1460]: No matching GPU found
dic 26 18:53:55 fedora /usr/bin/nvidia-powerd[1460]: Failed to initialize RM Client
Lif this is game related or gaming specific you might have better luck in #gaming-general
Li started running into issues by trying to run hogwarts legacy, but it's basically about getting my nvidia card to work
Lah ok then
Lcan i do a reinstall, not a rebase, without losing my user data if i have everything on the same partitiom?
LHey J0rge since you are the only one around atm do you have any suggestions to what i could look into to find out why im getting the greeter screen from sddm instead of the normal game mode? Even the return to game mode shortcut drops me back to the greeter screen on the steam deck.
Li'm also getting an error while trying to update Error in update script: 02-distrobox-user-update.sh, check logs for more info 
KThat means one of your distroboxes is failing to update, we don't make any by default, that script is just there to make things easier for people who do have them
KYou'll have to figure out why it's failing and then correct that
KYou can simply run
distrobox-upgrade --allKAnd look at the output
Lwell since i have no idea what even a distrobox is, i'm not sure what's going on
Li'll look at the output
KPowerd failing can be normal
KIt's dependent on your GPU
KThat's just how it works upstream
Li'm not exactly concerned about powerd, i just thought it could be a symptom
Lthe distrobox update gave me a nvidia error
Luh
LRiepilogo errori
-------------
Requisiti relativi al disco:
Necessario almeno 1MB di spazio aggiuntivo nel filesystem /usr/share/doc/libva-nvidia-driver.
-------------
Requisiti relativi al disco:
Necessario almeno 1MB di spazio aggiuntivo nel filesystem /usr/share/doc/libva-nvidia-driver.
Tdo you have bazzite-arch still?
Kdistrobox listLuhm how should i know if i have it?
_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
