Steam for Linux

Steam for Linux

L7vanmatre Sep 4, 2019 @ 9:48am
Proton not launching things, I see a possible solution, but...
I've been at this for about 4 or 5 hours I think, so I may miss some details in favor of some more recent ones.

Manjaro 18.0.4
NVIDIA GTX 1050Ti
i3-6100

Proton works just fine when the game is installed on the Linux partition, but I'm wanting to start the games from another partition that uses NTFS.

Yeah, I did use ntfs-3g to mount the drive. I did put it into fstab, and I'll put what I wrote just in case if I've miswritten that.

/dev/sdb1 /home/gary/Windows_HDD/ ntfs-3g uid=1000,gid=1001 0 0

Keep in mind before that, I did this

/dev/sdb1 /home/gary/Windows_HDD/ ntfs-3g uid=1000,gid=1001,dmask=022,fmask=133 0 0

And Steam said something like "Steam needs executable permissions to make this the library", so I deleted the last two options because of this answer: https://github.com/ValveSoftware/Proton/issues/35#issuecomment-414949271

And when I did that, it finally accepted the Steam folder I have on the Windows partition as the answer.

However, it still doesn't work. It still has the same effect back to when it was temporarily mounted and was under run/media/[stringofnumbersandletters]. It launches, and can install/uninstall, but can't launch via Proton, until I move the thing over to my Linux drive and then Proton works fine.

I've installed steam-Manjaro by itself, and Steam Manjaro + Steam Native, and also that "extra fix" thing and various other combos. None of them fix the issue.

I have logs if it helps. This first one is launching Rivals of Aether on the NTFS partition. It doesn't work here.
https://pastebin.com/8Y7XWZ7j

And this is logs (resuming a little after the first left off) for launching Bloons Tower Defense 6 on the Linux drive. It works here.

https://pastebin.com/4mhKw0Ub

(The game runs perfectly fine, I just kinda cut it off at the end there since I'm fairly sure that after that, it's not relevant.)

And I did move Rivals of Aether to the Linux drive, and it runs perfectly then. So it's either because it's running it off of another partition or an NTFS partition.

But after this, I am completely lost. I think I've done just about everything I remember finding on Google.
< >
Showing 1-8 of 8 comments
L7vanmatre Sep 4, 2019 @ 9:50am 
I noticed that there's a difference. It says the usual thing until it says
pid 3322 != 3321, skipping destruction (fork without exec?)
and then it starts to stop the game.

Unfortunately I don't know what pid 3322 nor 3321 is, nor the meaning of "fork without exec" nor even understanding what "skipping destruction" necessarily means.
L7vanmatre Sep 4, 2019 @ 9:51am 
Sorry I've forgotten the majority of the past several hours. After I'm done writing this, I'm going to take a break. I appreciate any help given to finding the heart of this issue.
Last edited by L7vanmatre; Sep 4, 2019 @ 9:52am
Aoi Blue Sep 4, 2019 @ 12:19pm 
Originally posted by L7vanmatre:
I noticed that there's a difference. It says the usual thing until it says
pid 3322 != 3321, skipping destruction (fork without exec?)
and then it starts to stop the game.

Unfortunately I don't know what pid 3322 nor 3321 is, nor the meaning of "fork without exec" nor even understanding what "skipping destruction" necessarily means.
That is a normal info line.

PID means Process ID (i.e. what running program/thread)

Skipping destruction means it's not deleting a memory segment yet because it is still in use.

"Fork Without Exec" means that a new process might have been spawned without running the exec routine. When done improperly this can create hung Process IDs, so it gives this warning message to look out for that possibility.

Wine uses a separate internal exec function instead of kernel exec function when executing new programs, so this is likely normal and unrelated to your issues.

Your issues are clearly with mounting your NTFS filesystem wrong.
The author of this thread has indicated that this post answers the original topic.
L7vanmatre Sep 5, 2019 @ 11:00am 
Originally posted by Aoi Blue:
Originally posted by L7vanmatre:
I noticed that there's a difference. It says the usual thing until it says
pid 3322 != 3321, skipping destruction (fork without exec?)
and then it starts to stop the game.

Unfortunately I don't know what pid 3322 nor 3321 is, nor the meaning of "fork without exec" nor even understanding what "skipping destruction" necessarily means.
That is a normal info line.

PID means Process ID (i.e. what running program/thread)

Skipping destruction means it's not deleting a memory segment yet because it is still in use.

"Fork Without Exec" means that a new process might have been spawned without running the exec routine. When done improperly this can create hung Process IDs, so it gives this warning message to look out for that possibility.

Wine uses a separate internal exec function instead of kernel exec function when executing new programs, so this is likely normal and unrelated to your issues.

Your issues are clearly with mounting your NTFS filesystem wrong.
Alright, thank you for the information, it's helpful!

I'm not exactly sure what the issue would be, though. When I did this exact thing on the Live USB, it worked perfectly. Doing the same thing on the installed version suddenly seems to make an issue, one that I'm not sure why.

And that's the weird thing. Steam can access the filesystem, write to them (same as me, the user), but doesn't seem to let Proton use it. Hopefully the github link I was provided will help!

Originally posted by Marlock:
https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
Thank you very much! I shall try this!
L7vanmatre Sep 5, 2019 @ 11:44am 
Originally posted by Marlock:
https://github.com/ValveSoftware/Proton/wiki/Using-a-NTFS-disk-with-Linux-and-Windows
THANK YOU!

Turns out the drive was mounted okay (the thing the guide itself said seemed to make it read-only, but I am on Manjaro after all. I just did somewhat what I did in the OP to make it read and writable again), but the thing at the very end ("Preventing NTFS Read Errors") seemed to have fixed the issue I was having!

Really wish this came up on Google when I was researching everything. Thank you so much!
Marlock Sep 6, 2019 @ 4:58am 
I'm glad it was enough to fix your issue! :steamhappy:
Interesting. Topic Bookmarked.
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Sep 4, 2019 @ 9:48am
Posts: 8