Hello @ctjlewis, the steam package used to unconditionally gather all stdout and stderr output to /tmp/dumps/<username>_stdout.txt. This has been removed from newer steam packages, but you can still use regular stream tools like running steam 2>&1 | tee /path/to/log to get similar functionality. All terminal spew from launched games should end up there unless the game engine intercepts it earlier to go to a game-specific logfile.
Thank you so much. Thoughts on adding a CLI flag to the launcher, like --log <location>? Would consider submitting a PR.
Nothing extracted yet.
From the time that a user clicks the "Play" button to the time that the game runs, everything must be clearly logged in one place for a consistent record of events.
My issue is that the "Play" button displays the necessary prompts (activation codes etc), but the game immediately exits when Steam tries to launch it. There is a series of logs in
~/.steam/steam/logs, but none of them seem to contain any information about why the game exited, or what stage in the launch process this occurred at. As a matter of debugging, the only thing I can really do is shrug my shoulders, because there is no obvious log or dialog displaying what went wrong.