ValveSoftware / ValveSoftware/Proton
Proton fails to populate dosdevices
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
I have a separate ext4 drive that's exclusively for my games, but when I try to install games with Proton to it none of them launch, becuase pfx/dosdevices is empty. Any combination of game and proton version has so far failed to start without manually populating pfx/dosdevices with the expected symlinks. I have two library folders, one in the default .steam-location and the other on the second drive. Installing games to .steam works fine.
All games give error logs similar to this: https://gist.github.com/Kimplul/e8d7fb4dcb2119a9cf6e3893258b812c
And here's my system information: https://gist.github.com/Kimplul/9a5ccd79801550c45d1d2f8cbc0e38da
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 reviewing the linked Proton error log and system-information gist, then reproduce installation to the secondary ext4 Steam library and compare it with the working .steam library. Trace why pfx/dosdevices remains empty; done means the expected symlinks are created automatically and the affected games launch without manual changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100