-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SteamLibrary keeps being recreated on microSD card despite being removed in SteamOS and in Desktop Mode #95
Comments
I did some digging and realised some people were having the reverse problem on the Steam github. While I can't seem to remove my library folder, they can't add a new one. I've looked at my
This happened after I deleted the folders from the SD card manually. I guess it's possible that rEFInd is re-creating the library folders, which Steam then recognises when it scans for external media on boot? |
I don't think this error has anything to do with rEFInd, but I'd be happy to help you try to troubleshoot it. |
What OS are you using (if any) on the SD card? |
I think I should only have Batocera on the SD card. It's also added as an EFI to load in the GUI. edit: I forgot to say, thank you for offering to help with this even though it may not have anything to do with rEFInd :') |
I recently used rEFInd to fix a triple booting issue I had thanks to SteamOS 3.5. However, after using the rEFInd repo to fix the issue about a week ago, I realised SteamOS kept registering a Steam Library folder on my microSD card (and setting it as default).
I've tried removing the library through the SteamOS interface, and through manually deleting the libraryfolder.vdf file in the microSD card. However, upon rebooting into SteamOS, the library reappears as if it was never deleted. I think this might have something to do with rEFInd, as it's the only thing that's really changed in my Steam Deck config.
I've tried to
git status
the repo I used, but apparently, my branch is up to date withorigin/main
despite being a week old, so...The text was updated successfully, but these errors were encountered: