If a process is invoked along with %command%, Steam will show user as in-game even after %command% has quit

steamclosed reviewedNot a bug

ValveSoftware/steam-for-linux#2539 · opened 2013-05-30 by Tea23 · updated 2013-05-31 · 2 comments · github

TTea23 2013-05-30 github

I experimented with launch options and trying to kill compton (a compositing manager for window managers like Openbox). So I set the launch options for one game to be killall compton && %command% && compton. In theory this would kill compton, run the game and then run compton again - and it works a treat.

Except Steam latches on to the compton process and continues to count me as in-game for as long as it's running.

You can combine this with anything. Maybe you run gdb %command% to try and debug your game. The game itself quits, but gdb hangs your Steam status.

Ggdrewb-valve maintainer 2013-05-30 github

This is expected, Steam runs the given command line and waits for it to finish. If it doesn't finish then the 'game' is still running. %command% is just a text-replacement option, it doesn't direct Steam to monitor a subprocess.

Jjorgenpt 2013-05-31 github

@Tea23, and to your original question, does adding a & after 'compton' fix it? That makes it go into the background.

Making the command:

killall compton && %command% && nohup compton &

Might solve your problem. (The `nohup' prevents compton from quitting when Steam quits.)

Nothing extracted yet.