Skip to content
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

[Feature Request] Allow multiple Linux user accounts to share a single game installation using proton #10790

Closed
jessecambon opened this issue Apr 18, 2024 · 2 comments

Comments

@jessecambon
Copy link

Please describe your issue in as much detail as possible:

It is not possible for multiple Linux user accounts to run games from a single shared steam library with proton due to a file permissions issue. It would be very valuable to fix this issue for those looking to share games on a single system (family sharing, etc.). Having multiple installations of the same game on a single system isn't an attractive solution due to the large size of many modern games.

This issue has been documented previously in ValveSoftware/Proton#4820, #3942, and #6958

There is also a PR to address this issue here: ValveSoftware/Proton#4861

Tagging some of the users from the above mentioned issues here:

@crlsgms @shelterx @Maykin-99 @geoffryan @Nomz420 @VannTen @Adam-Saeed @artrsnd @kisak-valve @dottgonzo @alexbarcelo @thepowersgang @EgorIII @kon14

Steps for reproducing this issue:

  1. Install steam library games in a folder to be shared between multiple Linux users.
  2. Grant Linux users file access to the shared folder.
  3. Attempt to run a game from the shared folder using proton with the different Linux user accounts.

The resulting error looks like this:

wine(server): /opt/games/Steam/steamapps/compatdata/430190/pfx is not owned by you
@kisak-valve
Copy link
Member

Hello @jessecambon, please do not intentionally open duplicate issue reports.

Closing as a duplicate of ValveSoftware/Proton#4820.

@kisak-valve kisak-valve closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
@jessecambon
Copy link
Author

Hi @kisak-valve, understood but that issue and linked PR are three years old at this point and it wasn't clear that they were being tracked. The PR is a very small code change so it would be helpful as a starting point to know if this is a workable solution or what else would be required.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants