opened
hcorion
username_0
I have two steam library folders, one on my SSD, located at ~/.local/share/Steam, and one stored on my HDD, mounted at `/mnt/hd`, the HDD one is set to default. It seems that Photon installs to the default folder, `/mnt/hd/SteamLibrary-linux/steamapps/common/Proton 3.7/`.
Trying to launch A Hat in Time fails with the following
```
Traceback (most recent call last):
  File "/mnt/hd/SteamLibrary-linux/steamapps/common/Proton 3.7/proton", line 89, in <module>
    tar.extractall(path=basedir + "/dist")
  File "/usr/lib/python2.7/tarfile.py", line 2081, in extractall
    self.extract(tarinfo, path)
  File "/usr/lib/python2.7/tarfile.py", line 2118, in extract
    self._extract_member(tarinfo, os.path.join(path, tarinfo.name))
  File "/usr/lib/python2.7/tarfile.py", line 2202, in _extract_member
    self.makelink(tarinfo, targetpath)
  File "/usr/lib/python2.7/tarfile.py", line 2280, in makelink
    os.symlink(tarinfo.linkname, targetpath)
OSError: [Errno 22] Invalid argument
```
Trying to launch a game on a different drive from the main install fails
issue
created
Mikerr1111
username_1
Check to make you have Python 3 installed.
comment
created
sbmn
username_2
Exact same issue. Python 3 is installed and the drive has rwx perms
comment
created
hcorion
username_0
the issue might be with ntfs, @username_2 what format is your secondary drive?
comment
created
meowmeowfuzzyface
username_3
Same issue on Ubuntu 18.04.1.  Error log contains the exact same error.  Tried with Doom (2016), Quake, and Doom 2.  OS drive is ext4, games are installed on an NTFS drive mounted with the following options:
ntfs-3g defaults,exec,uid=1000,gid=1000,windows_names,locale=en_US.UTF-8 0 0
comment
created
meowmeowfuzzyface
username_3
Removing "windows_names" from fstab fixed it.  Left locale in there without problems.  On a side note, the official Ubuntu documentation for mounting NTFS drives says to use the windows_names option, so I think this is an issue that will come up a lot in the future for dual-booters.
comment
created
TheGreatMcPain
username_4
The only issue that would come up is when windows can't move, copy, or delete a file because it has a character in it's name that Windows doesn't like.  I do believe windows can still open those files like normal though.
comment
created
meowmeowfuzzyface
username_3
I meant that this is an issue that I think a lot of users will run into because the official Ubuntu documentation instructs users to use the "windows_names" mount option in the fstab entry, and Ubuntu's automated method to add NTFS drives to fstab includes the "windows_names" option by default.  But it's good to know that removing it shouldn't cause any major issues on the Windows installation.

Thank you both for your help.  I hope this solution works for OP as well.
comment
created
sbmn
username_2
Solution worked.
comment
created
peterson432
username_5
Try to run ntfs-3g command without names or locale, 
ntfs-3g defaults,exec,uid=1000,gid=1000
comment
created
kisak-valve
username_6
Noted at https://github.com/ValveSoftware/Proton/issues/2775#issuecomment-499477244, upstream wine has prefix ownership check which may have been added due to past issues with the user creating the prefix as root and then having issues accessing the prefix later.

Running Steam as root is explicitly unsupported and blocked in its startup script, so that particular scenario would require a bad actor to make a folder that the current user can't manipulate, but there may be other methods leading to permission issues that need to be considered.
comment
created
madewokherd
username_7
We should at least be able to detect some of these situations (can't create c: symlink, can't create a prefix with the correct ownership, existing prefix has wrong ownership) and report an error. Is there a way we can report an error message back to steam, or failing that can we assume the presence of something like xmessage or zenity?
comment
created
RockyTV
username_8
IIf it is of any help, I have some log files and crash dumps after I tried running Elder Scrolls Online on my Linux install on an NTFS drive mounted with `windows_names`.



[eso_crash.zip](https://github.com/ValveSoftware/Proton/files/3935116/eso_crash.zip)
comment
created
Wenzel
username_9
Hi, got the same issue, removed `windows_names` and it works fine now.

Thanks !
comment
created
SomeoneIsWorking
username_10
On Ubuntu + Lutris. I had to do the opposite to solve it. Which was to add the `windows_names` that wasn't there before. 
Can't figure out how to do it in kubuntu though because it is mounting as fuseblk and unmounting and remounting with ntfs-3g -o windows_names didn't help
comment