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

Can't launch Windows games installed on another drive #35

Closed
PixeLInc opened this issue Aug 22, 2018 · 14 comments
Closed

Can't launch Windows games installed on another drive #35

PixeLInc opened this issue Aug 22, 2018 · 14 comments

Comments

@PixeLInc
Copy link

PixeLInc commented Aug 22, 2018

I'm trying to launch a supported game (or any other windows game) from steam play but it keeps erroring out with

 wine: /mnt/games/SteamLibrary/steamapps/compatdata/698780/pfx is not owned by you

I've tried setting a umask for everyone to read,write, and execute , and a uid/gid with my user, both of which didn't work.
The uid/gid wouldn't let me mount the drive with steam, and the umask returns

OSError: [Errno 1] Operation not permitted: '/mnt/games/SteamLibrary/steamapps/compatdata/698780/pfx//drive_c/Program Files (x86)/Steam/steamclient.dll'

I'm using an NTFS Drive that is mainly used for windows games so only windows normally touches it.
I'd also like to note, if I move the install folder to my local drive which is an ext4 (Arch) it runs great.
But I'd rather not switch my other drive to ext4 or anything like that if I don't have to.

Is there something I'm missing? Something I haven't tried or I'm just being too dumb to notice lol

@linkjay
Copy link

linkjay commented Aug 22, 2018

The problem is NTFS does not like to cooperate with the kernel's mounting.

Try installing ntfs-3g and mounting it that way. If you setup an automatic mount in your fstab, set the partition type to ntfs-3g instead of ntfs for it to work on boot.

Mounting it through ntfs-3g, even as root, should allow your local user to read/write files on the drive. Overall, ntfs-3g just provides more options and support for the ntfs on Linux.

See this for more info for any distro (not just arch): https://wiki.archlinux.org/index.php/NTFS-3G

@PixeLInc
Copy link
Author

I just tried that, mounting via ntfs-3g and setting it in my fstab as well and it doesn't seem to have any effect.
The issue above is, I can read, write, and execute any file on the drive perfectly fine. I install games on it and remove stuff easily but it just doesn't start the windows game via steam play.

Always throws that 'not owned by you' error.

@linkjay
Copy link

linkjay commented Aug 22, 2018

Try adding these arguments to your ntfs-3g options line.

uid=userid,gid=groupid

Where userid and groupid can be found by doing

cat /etc/passwd | grep USERNAMEHERE

and it will be like this

img

In the highlighted area: left of colon is userid and right of colon is group id

@PixeLInc
Copy link
Author

Hm, well that does seem to be working, wow!
I tried the uid/gid thing before but maybe the ntfs-3g thing helped it along the way.

Thanks for the help :)

@oblitum
Copy link

oblitum commented Aug 27, 2018

But, is this the proper fix? I've always used the NTFS drive for any kind of media and all files stored in it are created as owned by root:root, and that's fine, because I don't want my particular current user:group associated to files created on this drive, because I can use it in any other machine I own. Now if I start mounting it with given user:group, files created in it will be owned by that user right? Which may not exist in other machines.

@oblitum
Copy link

oblitum commented Aug 27, 2018

I'm asking because, one can write/read/execute just fine with default mounting behavior, dunno why Proton/Wine NEEDS the files to be owned by users in specific...

@oblitum
Copy link

oblitum commented Aug 28, 2018

Hmm, nevermind, NTFS doesn't work that way when on Linux, the uid/gid setting just makes everything in the drive owned by the given user, not something file specific.

@YaLTeR
Copy link

YaLTeR commented Aug 28, 2018

Just ran into this. Very odd because anything else, including launching stuff with regular wine, works fine. Please at least put the fix somewhere visible, I imagine I'm far from the only person to try mounting their Windows Steam library from an NTFS drive.

@parkerlreed
Copy link

What are your mount options? This works fine here (automounted by udisks2/Plasma)

/dev/sdb1 on /run/media/parker/TBerculosis4 type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)

@YaLTeR
Copy link

YaLTeR commented Aug 28, 2018

I just had defaults in /etc/fstab. I added uid and gid now as detailed in the beginning of the thread but I haven't tested it yet.

@oblitum
Copy link

oblitum commented Aug 28, 2018

The uid/gid setting worked for me. I also just had defaults on fstab before.

@sir-maniac
Copy link

@oblitum actually ntfs-3g does support mapping individual users, however, it's non-trivial to set up.

@sir-maniac
Copy link

sir-maniac commented Aug 30, 2018

Wine uses a colon in it's $WINE_PREFIX/dosdevices folder, and NTFS seems to have trouble supporting this.

A possible workaround for this is to move the 'SteamApps/common/Proton 3.7' and 'StreamApps/compatdata' to a non-NTFS drive, and creating symbolic links in their original locations. This solution worked for me.

Also, make sure the output of 'ulimit -c' is a large number, like maybe 8192 or larger.
See Here to change that limit.

EDIT: see also #82 (comment) and #35 (comment)

@oblitum oblitum mentioned this issue Nov 3, 2018
2 tasks
Maykin-99 pushed a commit to Maykin-99/Proton that referenced this issue Jun 11, 2021
Build proton on Github actions (thanks vaslabs!)
@Bandito11
Copy link

Bandito11 commented Aug 7, 2022

If using udisks2, what worked for me is adding rw,uid=userid,gid=groupid to the lists of parameters in /etc/fstab

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

7 participants