When Steam is in this state, after leaving it in the state for several minutes, please kill -11 the Steam process. It will crash it, generating a crash ID. Send us the ID and we can look into it.
I'm having a problem getting it to replicate. Now, when I File > Restart Steam, I wind up getting a segfault.
Shutting down. . .
/home/josh/.local/share/Steam/steam.sh: line 341: 19734 Segmentation fault $STEAM_DEBUGGER "$STEAMROOT/$PLATFORM/$STEAMEXE" "$@"
I'll keep trying to replicate accurately.
On the bright side, the initial bug seems to have resolved itself.
Issue update: I think I found part of the issue. While I cannot get it to replicate the hang (so I will close this until I can replicate it), I did find the following occurring at random:
CAsyncIOManager: creating I/O worker thread
CAsyncIOManager: creating I/O worker thread
Installing breakpad exception handler for appid(steam)/version(1358979709_client)
Installing breakpad exception handler for appid(steam)/version(1358979709_client)
CAsyncIOManager(0xd5915b40) send on fd 82 failed with errno 11 (Resource temporarily unavailable)
I know CAsyncIOManager is responsible for much of how Steam closes. Not sure if that error has anything to do with it hanging at times.
New update: Just encountered an instance where it wouldn't shutdown. It seems to hang on steam-cloud-sync. I attempted to kill the process with the kill -11 as per suggestion and it didn't kill steam.sh (but it killed the other steam process).
My updated system info: https://gist.github.com/45ed161ede54ebc30909 . The dump should be somewhere near the bottom of the list.... which is so very long.
I tried the last 5 dumps on your list and they are all texture problems -- none related to this. Are you sure you got it to dump properly (and yes, note you should kill -11 the steam process, not steam.sh)
I did kill -11 the steam process not the steam.sh. Not sure why it didn't make a dump. That's frustrating.
It should report a Crash ID directly in Steam's console output when you kill -11 (so best to run it from somewhere you can get that output).
Interesting. I see what happened. It segfaulted when I did the kill -11 on the Steam process.
Also happened to me. Once it segfaulted, now it was stuck at shutting down for a long time. It didn't respond to kill -11. Either time no dumps were generated. Seems to happen randomly…
Yeah. I've been logging off and on so many times over the past hour.
Is this still occurring with the latest update?
It doesn't seem to be. If it does, I'll reply here and potentially re-open.
Nothing extracted yet.
Specs: https://gist.github.com/45ed161ede54ebc30909
I installed a skin (they're fixed....ish) and went to restart and I discovered that steam is taking a LONG time to shut down.
Right now, I'm sitting on over 3 minutes to shut down. In terminal, it just hangs on "Shutting down. . ."
![Screenshot from 2013-01-23 22:51:07]()