When starting CS:GO using the Steam Linux Runner the game starts as expected, but Lutris will consider it exited after a second.
Unfortunatly the “Switch resolution to” and “Turn off monitors except” features rely on the tracking by Lutris.
I’ve tried adding csgo_linux64 to the “Include processes” without success.
The log output is:
lutris-wrapper: Counter-Strike: Global Offensive
Running gamemoderun /usr/bin/steam steam://rungameid/730
Initial process has started with pid 40655
Game is considered started.
Running Steam on fedora 32 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Steam client's requirements are satisfied
/var/home/username/.local/share/Steam/ubuntu12_32/steam steam://rungameid/730
Game is considered exited.
Initial process has exited.
All children have exited.
Exit with returncode 0
2020-07-27 23:38:04,811: Full shutdown prevented
2020-07-27 23:38:06,324: Game still running (state: running)
2020-07-27 23:38:06,324: Stopping Counter-Strike: Global Offensive (steam)
> the game is executed and playable afterwards
The same happens here:
I just encountred this kind of problem with stalker: call of pripyat, other games in my library starts without any issuse.
this is log:
Running /home/ricky/.local/share/lutris/runners/wine/lutris-5.7-8-x86_64/bin/wine /home/ricky/.local/share/lutris/runners/winesteam/prefix64/dosdevices/…/drive_c/Program Files (x86)/Steam/steam.exe -no-cef-sandbox -console steam://rungameid/41700
Initial process has started with pid 36973
Game is considered started.
ILocalize::AddFile() failed to load file “public/steambootstrapper_english.txt”.
Game is considered exited.
Initial process has exited.
All children have exited.
Exit with returncode 0
I think something went bad with last steam patch, since I was able to play this game last week.
I’m on pop_os! 20.04.