ValveSoftware / ValveSoftware/Proton
Some proton utility commands hang when running on nfs
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Setup:
- Updated Fedora 28 x86_64
- mesa 18.0.5
- Intel Corporation HD Graphics 5500
If I install the game to my local disk (~/.local/share/Steam) Starwars Battlefront II (and others) runs fine.
I have an autofs/nfs share (/net/berrier/steam) on another computer (backed by a 32bit xfs filesystem) and when I run a proton game (I've verified this with a few proton games), the following commands hang indefinitely:
python2.7 /net/berrier/steam/steamapps/steamapps/common/Proton 3.7/proton run /home/wberrier/.local/share/Steam/legacycompat/iscriptevaluator.exe --get-current-step 6060
python2.7 /net/berrier/steam/steamapps/steamapps/common/Proton 3.7/proton getcompatpath /net/berrier/steam/steamapps/steamapps/common/Star Wars Battlefront II
As a sidenote, I can run steam under wine and access this same nfs share just fine. I really think it's something with the utility commands that are hanging with this setup.
I've also seen this behavior on a machine running Fedora 27.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the two Proton utility commands shown in the report, comparing the NFS path with the local Steam path. Trace the Proton script entry point and its handling of getcompatpath and run, then identify why the commands block on NFS. Done means both commands complete reliably with the reported NFS setup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, python
- Domain
- cli, networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100