I'm trying to run games using Proton on an NTFS partition.

[kolzar]

After a long time, I have no other ideas how to annoy people on the forum. And so, after 3 distributions (Ubuntu, Kubuntu, Manjaro-current), I have a specific misunderstanding of the situation. The fact is that every time I try to run the game through Proton, it simply does not want to run. I'm unpacking all the games on an additional NTFS partition, because there's other stuff for Windows as well. After reading the recently written material on GitHub regarding this situation, I found myself in a complete misunderstanding of the situation and inexperience. As I understood from that guide on GitHub, you need to mount the Linux partition completely, but the problem is that it was already mounted when I installed the OS. But when I installed Ubuntu, and I screwed up, it looks like. the scheme (running Proton games on an NTFS disk), then everything worked for me.

OS - Manjaro KDE 21.2.4
GitHub guide - https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
All system requirements are met, so there's no point asking for them

I'm terribly sorry if I make someone waste their time on a dumb like me

[Marlock]

mandatory disclaimer:

using NTFS is possible but not recommended because it performs slower, is more vulnerable to data loss, is less reliable in general than normal linux partitions like ext4

that being said, please try to explain which of the instructions on Valve's github wiki were clear and which made you insecure on how to move forward

also send the content of the text file "/etc/fstab", or at least the relevant line (there should be one for your ntfs partition but it may still need a few special parameters to make proton happy)

ps:
reading of your original post makes me think that you might be confusing "mounting" (create an arbitrary empty folder and mount a partition to it so the patition contents are visible there) with "partitioning" and/or "formatting" (changing/creating new partitions to use)

pps: did you change windows settings to avoid it leaving the NTFS partition in a dirty state when windows powers off? this should avoid a few issues down the line with scary fdisk checks on windows

[kolzar]

First of all, I used two sources, this is a page on ProtonDB[www.protondb.com] and GitHub[github.com]

Everything I could see made me doubt. Since the beginning of the free use of Proton on Ubuntu, when I only registered one partition to install the OS, and later I could freely use NTFS partitions. Then the fact that when installing Kubuntu and Manjaro, I prescribed partitions manually, like:
/disk500
But for some reason, after such manipulations, Proton refused to work on subsequent distributions.

/etc/fstab:
UUID=FE78746C78742595 /home ntfs defaults,noatime 0 2

It is quite possible that I really confuse the concepts of "mounting", but it seems to me that it's still a matter of the rights of the partition on which I want to install games, because there is an owner and a group there - root (But at the same time native games run and work on the same partition as Proton).

I also tried to use sudo chown, but apparently it was useless...

At the expense of Windows and NTFS, I have no idea what it's about, since I'm conditionally like a regular user: I created partitions when installing windows, they became NTFS. Next, I recaptured a 32 GB partition from one hard disk, and installed Linux on it, while formatting the partition in ext4.

[Marlock]

here are the key concepts you probably need for understanding your issue...

NTFS is a windows partition format, not a UNIX partition format (used by Linux, BSD, Mac, Android, ...)

As such it doesn't have a way to store file/folder permissions (read, write, execute) for each object, which Proton needs

Proton, unlike normal WINE and other linux software, is even pickier... it requires you to be the "owner" of the folders/files that make up a game's proton prefix folder... which is also a UNIX property not properly supported by NTFS format


You can chown and chmod everything in an NTFS partition after it's mounted, but it will not have a practical effect...

ps: it will silently revert, whereas IMHO it should produce an error or at least a warning message


The workaround proposed by Valve is to fake full read+write+execute permissions AND user ownership of everything on the NTFS partition when you mount it... (and this should happen again and again automatically at boot, for convenience, instead of just once on request)

the default is to mount NTFS as read-only or as read+write, so that means tweaking the auto-mount options... which is what the /etc/fstab editing is for, defining custom mount option that will be remembered after reboot

which options?
read+write+execute AND owner user ID


this also explains why NTFS is impossible to use as the main linux partition, even if it can be used as secondary storage... it works for files just fine, but has several limitations for running executables, let alona a full linux OS from it


i need to get back to work now, but maybe it is enough to put you on track...

you basically need to edit that fstab entry to add the correct non-default parameters

ps:
1) do NOT replace the existing entry for the main system drive
2) do NOT use NTFS as your entire /home partition, only as a subfolder to it at most... the entry you pasted in the last reply is worrying...

/etc/fstab:
UUID=FE78746C78742595 /home ntfs defaults,noatime 0 2

[BezaoBuilder]

Add the uid, gid and umask parameters as specified in Valve's guide on GitHub.

[Bloo Alien]

Originally posted by Marlock:

/etc/fstab:
UUID=FE78746C78742595 /home ntfs defaults,noatime 0 2

O my! That is scary!

[kolzar]

What do you want from an inexperienced person who is still learning a new OS for him after Windows? Okay, can I fix that, or need to reinstall system?

[Marlock]

I don't even know what happens if you reboot with that...

if your system is working at all, then you're in luck, and can edit the entries back into shape

the only problem is I'm not sure how the correct entry should look like exactly (definitely not with your entire home directory in that NTFS partition)

ps: that's why you should always make a backup before editing system config files like fstab, so mistakes can be more easily fixed... Valve's guide should definitely tell you so in large letters