protonscr

Segmentation fault at start

steamopen Distro Family: Fedora
ValveSoftware/steam-for-linux#7466 · opened 2020-11-14 by diegogangl · updated 2021-01-11 · 3 comments · github
Ddiegogangl 2020-11-14 github

Your system information

  • Steam client version (build number or date): Package steam-1.0.0.66-2.fc33.i686
  • Distribution (e.g. Ubuntu): Fedora 33
  • Opted into Steam client beta?: [Yes/No] No
  • Have you checked for system updates?: [Yes/No] Yes

Please describe your issue in as much detail as possible:

When trying to run steam the "verifying updates" dialog pops up, and then steam crashes with a segfault.
Here's the output in the terminal:
https://gist.github.com/diegogangl/add97bfd454f727debad8baa39027c64

I'm running AMDGPU. The GPU is working and recognized by glxinfo.
I've also tried removing ~/.steam and ~/.local/share/Steam/, and I've tried steam --reset.

If I delete those directories, steam downloads and applies a big update. Then it crashes with the same error, and
any next calls to steam crash the same way.

Steps for reproducing this issue:

  1. Run steam
Kkisak-valve maintainer 2020-11-14 github

Hello @diegogangl, does any 32 bit OpenGL application like glxinfo32 from https://koji.fedoraproject.org/koji/rpminfo?rpmID=22417555 work? This sounds similar to #7453.

Ddiegogangl 2020-11-14 github

Hey @kisak-valve, thanks for replying so quickly. glxinfo32 also fails:

▶ glxinfo32 
name of display: :0
libGL error: MESA-LOADER: failed to open radeonsi (search paths /usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open radeonsi (search paths /usr/lib/dri)
libGL error: failed to load driver: radeonsi
libGL error: MESA-LOADER: failed to open swrast (search paths /usr/lib/dri)
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  152 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  60
  Current serial number in output stream:  59

However, none of the solutions in #7453 worked for me.