protonscr

client crashes calling EC_KEY_new_by_curve_name

steamclosed
ValveSoftware/steam-for-linux#7227 · opened 2020-06-27 by sherpya · updated 2020-06-27 · 1 comments · github
Ssherpya 2020-06-27 github

Your system information

  • Steam client version (build number or date): 1591251555
  • Distribution (e.g. Ubuntu): Debian sid
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

It has something to do with runtime libraries, using from my system the launcher
goes a bit further

tested with two different libcrypto

valgrind output:

==38729== Thread 18 CIPCServer::Thr:
==38729== Invalid read of size 4
==38729==    at 0x11F202E3: EC_KEY_new_by_curve_name (in /usr/lib/i386-linux-gnu/libcrypto.so.1.1)
==38729==    by 0x1E81CA04: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x1E81CEF9: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x1E7AA645: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x1DE94AD7: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x1DEAFEF9: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x1DFFEB37: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x1E000155: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/steamclient.so)
==38729==    by 0x136FB2BF: SteamThreadTools::CThread::ThreadExceptionWrapper(void*) (in /home/sherpya/.local/share/Steam/ubuntu12_32/libtier0_s.so)
==38729==    by 0x136F936A: ??? (in /home/sherpya/.local/share/Steam/ubuntu12_32/libtier0_s.so)
==38729==    by 0x136F966E: CatchAndWriteMiniDumpExForVoidPtrFn (in /home/sherpya/.local/share/Steam/ubuntu12_32/libtier0_s.so)
==38729==    by 0x136F96C0: CatchAndWriteMiniDumpForVoidPtrFn (in /home/sherpya/.local/share/Steam/ubuntu12_32/libtier0_s.so)
==38729==  Address 0x15 is not stack'd, malloc'd or (recently) free'd

Steps for reproducing this issue:

  1. start the client
Kkisak-valve maintainer 2020-06-27 github

Hello @sherpya, this issue is already being tracked at #7223. Closing in favor of the older issue report.

Nothing extracted yet.