-
Notifications
You must be signed in to change notification settings - Fork 173
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
Removing config/config.vdf
, reinstalling and logging-into steam causes games to think that steam isn't launched
#10842
Comments
@kisak-valve If this is a game-specific issue, should i keep this issue open here or should i directly reach to the devs? |
Note: I am indirectly answering the question from alexlnkp Your system information :
Please describe your issue in as much detail as possible:
Steps for reproducing this issue:
Note: I launched The Witcher 3 (via GOG) which I had installed with wine-staging a long time ago and I have no problems. |
@guix01 The glibc issue was reported to the developers by Peter Jung and is currently being worked on, don't worry about that too much. |
@alexlnkp Install Proton Experimental solves the problem. Thanks you very much! (Lib32-glibc 2.39-2 always locked) |
Good news! The issue just got MUCH worse. Before that it was just a strange oversight that did no harm, but now i can't play any of my games since they just wont launch! Funniest part is that this all started to occur once i updated my packages to these versions (note that lib32-glibc supposedly got fixed):
I assume this was the issue with the NVidia drivers themselves from the start, therefore i strongly suggest other people to not update yet and wait for the next version that is a bit more stable. EDIT: Another fun fact: if i try to launch Don't Starve in linux-native way and not using proton, then it launches and works. The real issue is with games that have NO linux-native releases, or with games that just work better with Proton I suppose i should move this issue to Proton repo instead, but honestly i'm extremely confused as to what is the root issue. This could be NVidia's 550.* drivers problem, could be Proton's, could be Steam's. EDIT2: After some more testing, i landed on another weirdness of this problem! If a game remembers it should be launched with proton, then it launches but with TERRIBLE, and i mean TERRIBLE lag. But, if i decide to turn on the forced compatibility on in the settings, then the game just... wont launch. Instead it launches unity crash handler(?) in case of ULTRAKILL or other games made with unity. |
Your system information
Please describe your issue in as much detail as possible:
Describe what you expected should happen:
I expected the game to launch.
What did happen:
Game didn't launch.
Steps for reproducing this issue:
rm ~/.local/share/Steam/config/config.vdf
I used Don't Starve for testing this.
Usually i use Proton Experimental for launching it, but this time steam forgot i forced compatibility layer with it (due to me removing config.vdf)
The text was updated successfully, but these errors were encountered: