(Linux) Chobby.exe-related process stays permanently alive after quiting from Chobby

[lhog]

Linux. After I have quit from Chobby, which I run from the CLI with primusrun mono Chobby.exe there is a permanently alive leftover process, that frequently spams following messages into the Linux console:

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

In the processes list it's seen as:

  PID TTY          TIME CMD
10231 pts/2    00:00:29 mono-sgen

This is a 100% reproducable.

mono -V
Mono JIT compiler version 4.8.0 (Stable 4.8.0.495/e4a3cf3 Mon Feb 27 08:30:18 UTC 2017)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
	TLS:           __thread
	SIGSEGV:       altstack
	Notifications: epoll
	Architecture:  amd64
	Disabled:      none
	Misc:          softdebug 
	LLVM:          supported, not enabled.
	GC:            sgen

I think chobby should clean up the side processes it has created before quiting.

[lhog]

There were recent changes to chobby wrapper that resolved the aforementioned issue, so leftover process is no longer in place.

That said after one quits Chobby there are still

[S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed.
[S_API FAIL] SteamAPI_Init() failed; unable to locate a running instance of Steam, or a local steamclient.so.

messages running in console. The difference with previous behavior is that with Ctrl-C you can stop that spam.

Still I think the proper behavior would be to self-terminate wrapper upon the chobby exit. No need to prompt a user for Ctrl-C action.

[Licho1]

I made it close steam wrapper when spring closes,this should fix this last issue. Will be released on next stable, reopen if it wont be fixed after deployment.