-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Bug] Soda 9.0-1 defaults to drive_c/users/steamuser #73
Comments
So i'm not the only one; panicked when all my games lost their saves and settings after upgrading to Soda 9.0-1 in my Bottle. Turns out it created a new windows user 'steamuser'. I'm not using any steam runtime settings, nor any other runners. Reverting to 8.0-2 restored paths to my user. |
My guess is this is due to changes on Valve's end. Soda is based on Valve's proton which is probably why you are seeing 'steamuser' being created despite not using steam. |
@mirkobrombin It looks like we need to release a new version with the latest upstream patches. |
Yeah I think it's time. Not sure if de-steamify is actually needed but it's fine to me |
I will make a pull request to update the runners, including the de-steamify-90 patch when I get the chance. |
Describe the bug:
After installing the Soda 9 runner the used user dir changed from users/MyUserName to a newly created steamuser.
Since i had been using Soda 8 before and it used the standard user dir, my guess is that this behavior is unintended.
Reproduce:
Change runner from Soda 8 (or any runner that uses the default user) to Soda 9.0-1
-> new dir steamuser gets created in (Bottle)/drive_c/users/
The text was updated successfully, but these errors were encountered: