Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.
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.
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!
Thank you very much! I shall try this!
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!