Comment # 12 on bug 988273 from Egbert Eich

(In reply to Dmitry Misharov from comment #11)
> It does, but I think this fix should be presented in default repo.

No.

The claimed 'solution' wasn't a solution but a workaround. It was not even
clear why the workaround actually worked as this was never investigated.
In comment #5 and #7 it is claimed that steam statically links against
libcrypto. The explanation given in the link provided in comment #7 explains
the situation around statically linked libs and provides a workaround which
doesn't require to touch other components of the system.
Yet, the backtraces shown in the links provided in the original bug description
contradict this static linking. 
Again, we cannot fix this issue in Mesa - we will not touch system components
to work around issues with proprietary 3rd party applications. It is just wrong
and  *will* *not* *happen*.
Some other workaround needs to be found which will remain local to steam.
Someone just needs to investigate this thoroughly and come up with a full
explanation and sensible workaround. I don't have the time for this presently -
sorry.