protonscr

can't launch steam -- steam.sh segmentation fault

steamopen Distro Family: Arch
ValveSoftware/steam-for-linux#12211 · opened 2025-07-17 by riverpaper · updated 2025-11-21 · 16 comments · github
Rriverpaper 2025-07-17 github

Your system information

  • Steam client version: latest steam package
  • Distribution: arch
  • Opted into Steam client beta?: not sure
  • Have you checked for system updates?: yes
  • Steam Logs: steam-logs.tar.gz
  • GPU: amd radeon

Steps for reproducing this issue:

run steam

steam.sh[216335]: Running Steam on arch rolling 64-bit
steam.sh[216335]: STEAM_RUNTIME is enabled automatically
setup.sh[216397]: Steam runtime environment up-to-date!
steam.sh[216335]: Log already open
steam.sh[216335]: Steam client's requirements are satisfied
/home/johnny/.local/share/Steam/steam.sh: line 928: 216464 Segmentation fault         "$STEAMROOT/$STEAMEXEPATH" "$@"
Rriverpaper 2025-07-17 github

it looks like these env vars aren't being set

Image
Jjrennie 2025-07-18 github

Those env vars are being set within the steam.sh script (line 28 for STEAMROOT and line 646 for STEAMEXEPATH). I suspect that something is wrong with the binary itself (e.g. ubuntu12_32/steam).

Fwiw, I'm seeing a similar crash. Though, I didn't reboot after there was a fairly large update, so I'll try a reboot and report back.

Jjrennie 2025-07-18 github

No longer crashes after reboot,

Llemonlambda 2025-08-08 github

I have this exact same problem on nixos

Ppinkseep 2025-08-14 github

I have the same problem on Fedora 42 KDE version.

Ddmknght 2025-08-23 github

I got similar problem on a Debian-based distro. Reboot "fixed" it for me.

Llemonlambda 2025-08-27 github

I got similar problem on a Debian-based distro. Reboot "fixed" it for me.

it randomly fixes itself for me. I have no clue why
Reboot never works.

Llemonlambda 2025-08-27 github

Running systemctl --user restart pipewire fixed it for me somehow

Ddmknght 2025-09-03 github

Running systemctl --user restart pipewire fixed it for me somehow

Oh so that's compatible problem with pipewire instead. Interesting (and sucks).

Llemonlambda 2025-09-05 github

It's very strange how this causes it as every other program can use pipewire fine

Rrytrix 2025-10-07 github

This occurs to me as well on archlinux, restarting pipewire (systemctl restart --user pipewire) always works. But I what I found interesting is that this only happens on window managers like sway and hyprland and not on gnome. I also ran gdb on the executable and noticed that this happens when accessing a pipewire specific 32bit library. I also noticed that adding a bluetooth audio device tends to cause the bug to occur again after restarting pipewire.

Ddmknght 2025-10-12 github

It happened to me only 1 time on XFCE (maybe because i use the speaker from my montior. It's not great, but it works). So I guess it has something with selecting audio channel from dota 2's side caused crashes which shouldn't be the DE/WM's specific problem.

Ppe200012 2025-10-12 github

I have the same problem on Gentoo Linux. Reboot and restarting pipewire did not work for me.

Bbeyond-1234 2025-10-15 github

I have this same problem on archlinux when nvidia GPU disabled(switch to iGPU in UEFI). Steam only works with dGPU enabled in UEFI. I'm using laptop with AMD Ryzen 7 8845HS + GTX 4060 btw.

ZzincOctober 2025-10-16 github

same issue, kubuntu, nvidia, I have the issue on 580 drivers but not on the open source drivers (1050 ti). so, breaking distro containment.

had this issue, fixed it by reinstalling the 580 drivers. kubuntu, 1050 ti.

CCtrlLuzzio 2025-11-21 github

I'm on CachyOS with Hyprland and I'm having this issue rn, running systemctl --user restart pipewire seems to work but obviously it's really annoying having to run this command every single time i want to open steam.

Idk if it has something to do with this wireplumber config i made for an ironbar script

monitor.alsa.rules = [
  {
    matches = [
      {
        "node.name" = "~alsa_input.*"
      },
      {
        "node.name" = "~alsa_output.*"
      }
    ]
    actions = {
      update-props = {
        "session.suspend-timeout-seconds" = 0
      }
    }
  }
]

EDIT: I removed the rule, rebooted my PC and now steam is working normally again (or at least it seems like it)

Nothing extracted yet.