Comment # 6 on bug 988273 from
(In reply to Ond��ej S��kup from comment #5)
> 
> i think steam binary uses steamclient.so and steamservice.so with integrated
> libcrypto into this two libraries ... and here might be incompactibility
> between steam and Mesa used libs
> 

What do you mean? Statically linked? I very much doubt this.

It could well be that we are seeing different versions of the same lib loaded
and functions from different versions being called for the same sha1
calculation.
What I still don't understand is that this also happens when nut using the
steam provided runtime.
Unless the openssl maintainer is aware of any issue with a recent version of
libcrypto, this needs to be investigated more thoroughly - by the steam package
maintainers: presently, I don't have the time for this.


You are receiving this mail because: