login
|
language
Български (Bulgarian)
čeština (Czech)
Dansk (Danish)
Nederlands (Dutch)
Suomi (Finnish)
Français (French)
Deutsch (German)
Ελληνικά (Greek)
Magyar (Hungarian)
Italiano (Italian)
日本語 (Japanese)
한국어 (Korean)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
Português-Brasil (Portuguese-Brazil)
Română (Romanian)
Русский (Russian)
简体中文 (Simplified Chinese)
Español (Spanish)
Svenska (Swedish)
繁體中文 (Traditional Chinese)
ไทย (Thai)
Türkçe (Turkish)
Українська (Ukrainian)
Help us translate Steam


https://gist.github.com/OlliC/af25d026126b99e1a34940b30108eed8
Im also running Linux.
Edit: This bug was also reported in the following thread: https://steamcommunity.com/app/222880/discussions/1/350544098386019059/
Two months without any official acknowledgement, hope is all we got at this point.
However it is good to see more Linux users confirming this bug, maybe it will get some attention.
This are the relevant logs from my last start:
Game update: AppID 222880 "Insurgency", ProcID 8477, IP 0.0.0.0:0
pid 8479 != 8478, skipping destruction (fork without exec?)
>>> Adding process 8496 for game ID 222880
>>> Adding process 8499 for game ID 222880
Game removed: AppID 222880 "Insurgency", ProcID 8499
8478 is insurgency.sh
8481 is insurgency_linux
8487 is gameoverlayui
Steam thinks that 8499 was the real game pid. But it was just a process spawned on startup. Could not figure out what it is. Iam looking for a way to see what this process is atm.
strace -f -e trace=process steam
The relevant part is this:
strace: Process 9357 attached
[pid 9357] execve("/home/gaming/.local/share/Steam/steamapps/common/insurgency2/crash_handler", ["./crash_handler", "9337", "http://crash.newworldinteractive"..., "0", "22907", "-1"], [/* 81 vars */]) = 0
Game removed: AppID 222880 "Insurgency", ProcID 9357
This is another crash_handler problem. There are already some threads about server problems with it. insurgency_linux spawns a crash_handler process that steam thinks is the game.
Prevent the crash_handler process from getting spawned
Go to your insurgency2 folder and type
chmod 644 crash_handler
I can confirm that removing execute permissions on crash_handler worked for me aswell.