On Sat, Jul 28, 2018 at 8:33 PM, Alan Grimes <[email protected]> wrote:
> A picture is beginning to emerge, after the reboot..
>
>
> It did not give a usable error message so I had panicked and probably
> cleaned more than I should have... 73% chance the underlying issue was a
> graphics driver version bump that SHOULD have been clearly reported, but
> wasn't, the remaining chance being something else that had become
> incompatible while I was trying to update this junk. =\
>
> There was a library that I had to downgrade to version 1.8, from 2.x,
> that cleared an error, so it tried to load,
>
>
> Now it gets stuck eternally on "Connecting Steam Account: [...]"
>
> The logs are split among about 10^3 (rough estimate) different files,
> all of which are extremely boring...
>
Can you not run Steam in a VM or container? Distributed binaries on
Linux being pinned to old library versions has always been an issue.
There was a period of time roughly 1.5yr ago where people were
claiming Valve/Steam/developers had learned better (I attribute this
instead to Ubuntu starting to maintain more recent libraries) but it
seems like everything is broken again.
It looks like the errors you posted are exactly this issue, and this
is the one way to fix it forever. In my case I wouldn't trust Steam on
my main system anyway and would have to run it in a VM.
Cheers,
R0b0t1
