search

ValveSoftware / SteamOS

SteamOS community tracker
1.61k stars 70 forks source link

Steam OS boot loop #1045

Open miki223 opened 1 year ago

miki223 commented 1 year ago

Your system information

Please describe your issue in as much detail as possible:

Describe what you expected should happen and what did happen. there is bug in Steam OS where if you delete or move /home/deck/.local gamepad ui straight up won't load it will get stuck in a boot loop it'll make it look like Steam OS is broken sadly i don't have the hardware to investigate the problem
but we had multiple people mess this up on the SteamDeck discord so please if this is too hard to fix at least warn people not to delete or move .local or more concerning the same seems to be caused by just deleting .cache folder the expected behavior is that Steam re-runs the first setup wizard connects to the internet & repairs itself or just re-creates the .cache folder & re generates the cache

Steps for reproducing this issue:

  1. go into Desktop mode
  2. delete or move the /home/deck/.local or /home/deck/.cache
  3. reboot
al12gamer commented 1 year ago

May we know why you've deleted the .local folder? The system needs this to function. Was it up and running fine after a recovery?

miki223 commented 1 year ago

May we know why you've deleted the .local folder? The system needs this to function. Was it up and running fine after a recovery?

yes i can certainly tell you why people encountered this issue one person tried to symlink shader cache to the SD card i guess they followed a bad guide & ended up losing the folder another tried to make the folder visible by removing the dot as they needed to access ~/.local/share/Steam/steamapps/common/ from WINE's file picker(to mod games) which by default does not show hidden files(this can be changed in the drives tab of winecfg) a visible symlink would have helped here we were able to fix the 2nd person's problem by simply putting the dot back from bootable media(not the recovery as it could not boot on the flash drive they had as i recall) the 1st ended up reimaging of course that fixed the problem

miki223 commented 1 year ago

i am curious if the erase user data option from the chainloader menu would have also fixed this