@mjevans BVerifyInstalledFiles: ubuntu12_32/steam is 6109487 bytes, expected 5547858 indicates a corrupt or damaged client. Running steam --reset should re-bootstrap the client as if it were the first run for your user, it should not affect the games you have installed.
I completely missed that. I really didn't want to run --reset and didn't include it in my troubleshooting steps since it clears a very difficult to enter password (it's quite long and has a few sequences of special characters which are difficult to verify when you can't see what you're typing in).
Yes, that fixed my issue entirely. I suppose the real problem is that it applied a verify files step, failed, and didn't require an over-ride (or explain how to edit the expected check size/sums) to continue trying anyway.
Nothing extracted yet.
[steam client] [regression] Steam for Linux now depends on NetworkManager and a managed connection which is up even when normal connectivity exists.
Steam for Linux used to work for me. After some time and system updates I once again decide to see what games can be played on Linux and discover that Steam no longer launches. Troubleshooting steps later I discover that Steam now not only depends on NetworkManager, but does not even TRY to go online without seeing an active connection managed by NetworkManager.
https://gist.github.com/mjevans/7063271
Desired solution:
Ignore underlying network connectivity via any method; just try to connect and see if it actually works.