-
Notifications
You must be signed in to change notification settings - Fork 86
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
Games not launching / low fps caused by _v2-entry-point missing execute permissions #656
Comments
Hello @strtgbb, In the common case, this is downloaded from steam with the execute permission enabled. Did you happen to use an unusual method to install Steam Linux Runtime? Maybe with a copy utility from an older install which didn't preserve file permissions in the process? |
I installed it from the EndeavourOS repos. |
I just remembered, I did change hard disks about a year ago, which would have involved a file copy. Nothing else got affected like this, and I think the issues started more recently than that as well. |
I remember moving my steam folder more recently. That must have been the cause of the failed launches. I think I was already having strange performance issues before that, I don't understand why those have also resolved with changing that permission. Would it be possible to have a better error message? Instant crash and no logs was frustrating to investigate. |
The Steam Linux Runtime cannot provide a better error message for its entry point not being executable, because its entry point is the first time it gets the opportunity to run code. If that's not executable, then no code from the Steam Linux Runtime will run at all - so no matter how much code we might write, it cannot help you. The Steam client (a higher layer) could potentially provide a better error message (or just silently fix it), but that would have to be a Steam client change, not a Steam Linux Runtime change. |
What about the |
Neither Steam nor the Steam Runtime provides an executable named |
This must have been a separate issue, which has apparently now been resolved by some other change - either something you changed, or an improvement in Steam, games or your OS. Not having +x permission on
If essential Steam Linux Runtime scripts aren't executable, then that is expected. PROTON_LOG doesn't do anything until Proton starts up, but if the Steam Linux Runtime scripts can't run, then we'll never get far enough to be attempting to run Proton. |
Affected Proton versions: All tested (5-8)
Affected Games: All but one tested. (The one that launched and ran well was (the) Gnorp Apologue)
Issue:
The execution permission is missing on the following file(s)
~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_*/_v2-entry-point
Background:
I've been having issues with low FPS (~6) for months, and more recently, games not launching at all.
PROTON_LOG=1 wasn't even logging anything.
I saw a tip to check Steam Runtime Diagnostics and I saw a permission error on _v2-entry-point.
I tried chmod +x on that file, and now my games launch with excellent performance.
I am using EndeavourOS, I don't know if this issue affects other distros.
The text was updated successfully, but these errors were encountered: