protonscr

What kind of permissions is needed for Proton to work properly with NTFS partitions under Linux?

protonclosed
ValveSoftware/Proton#7098 · opened 2023-09-14 by isadfrn · updated 2023-09-14 · 1 comments · github
1 matching comments, n / p to jump
Iisadfrn 2023-09-14 github

Hello folks. I am trying to use Proton on my Debian 12, first game I tried was:

Age of Mythology: Extended Edition using Proton Experimental, Proton 8.0-3 and Proton 7.0-6, This is the log and when click to start, the game seems to launch and then stop. Important to say that this game is installed on an NTFS disk and if used on Windows 11 (I have dual boot) it works.

======================
Proton: 1675326504 proton-7.0-6e
SteamGameId: 266840
Command: ['/mnt/7DC0D59A447B4B6D/SteamLibrary/steamapps/common/Age of Mythology/AoMX.exe']
Options: {'forcelgadd'}
depot: 0.20230808.56728
pressure-vessel: 0.20230804.0 scout
scripts: 0.20230804.0
soldier: 0.20230808.56728 soldier 0.20230808.56728
Kernel: Linux 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64
======================
wineserver: /mnt/7DC0D59A447B4B6D/SteamLibrary/steamapps/compatdata/266840/pfx is not owned by you
wine: '/mnt/7DC0D59A447B4B6D/SteamLibrary/steamapps/compatdata/266840/pfx' is not owned by you
======================

Then I downloaded Age of Empires using my EXT4 partition. It works like a charm.

======================
Proton: 1694112709 experimental-8.0-20230907
SteamGameId: 221380
Command: ['/home/isadfrn/.local/share/Steam/steamapps/common/Age2HD/Launcher.exe']
Options: {'forcelgadd'}
depot: 0.20230808.56699
pressure-vessel: 0.20230804.0 scout
scripts: 0.20230804.0
sniper: 0.20230808.56699 sniper 0.20230808.56699
Kernel: Linux 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64
Language: LC_ALL None, LC_MESSAGES None, LC_CTYPE None
Effective WINEDEBUG: +timestamp,+pid,+tid,+seh,+unwind,+threadname,+debugstr,+loaddll,+mscoree
======================
fsync: up and running.
wine: RLIMIT_NICE is <= 20, unable to use setpriority safely
1882.229:0028:002c:trace:seh:install_bpf Installing seccomp filters.
1882.229:0028:002c:trace:seh:check_bpf_jit_enable enabled 0x31.
1882.230:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\wineboot.exe" at 0000000140000000: builtin
1882.231:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernelbase.dll" at 000000007B000000: builtin
1882.231:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernel32.dll" at 000000007B600000: builtin
1882.232:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0000000228280000: builtin
1882.233:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ucrtbase.dll" at 00000002C7470000: builtin
1882.233:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\sechost.dll" at 00000001EAF60000: builtin
1882.233:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\advapi32.dll" at 00000001D8C90000: builtin
1882.233:0028:002c:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ws2_32.dll" at 0000000370F70000: builtin
1882.258:0030:0034:trace:seh:sigsys_handler SIGSYS, rax 0xffff, rip 0x600000000005.
1882.258:0030:0034:trace:seh:install_bpf Seccomp filters already installed.
1882.259:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\services.exe" at 0000000140000000: builtin
1882.259:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernelbase.dll" at 000000007B000000: builtin
1882.259:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\kernel32.dll" at 000000007B600000: builtin
1882.260:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\msvcrt.dll" at 0000000228280000: builtin
1882.261:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\ucrtbase.dll" at 00000002C7470000: builtin
1882.261:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\sechost.dll" at 00000001EAF60000: builtin
1882.261:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\advapi32.dll" at 00000001D8C90000: builtin
1882.261:0030:0034:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\rpcrt4.dll" at 0000000368420000: builtin
======================

It seams to me that my NTFS partition needs some extra permissions, can you clarify what kind of file access is needed for Proton to work properly? Thank you in advance!

Kkisak-valve maintainer 2023-09-14 github

Hello @isadfrn, in general, wine requires that the wineprefix folder used with it must be owned by the user running wine to prevent an entire category of hard to diagnose issues. Proton inherits this behavior.

It's likely that the mount options used with your NTFS partition is forcing all files written to it to look like they're owned by a different user.

There's enough quirks with using NTFS that the general recommendation is to use a Linux native filesystem instead of it, but that written, there are some community provided suggestions at https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows/.

This specific issue is already being tracked at #4820. Closing in favor of the older issue report.

Proton versions

Launch options

DLLs