search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.21k stars 174 forks source link

[SOLVED] [Steam Client] Crashing at startup - Segmentation fault, line 756 - Arch Linux #4340

Closed SALVOuankeBALDO closed 8 years ago

SALVOuankeBALDO commented 8 years ago

Hello all. Recently, after days of not booting steam (several system upgrades were done in the meantime), I've encountered problems in starting the client. With or without STEAM_RUNTIME=0, I run in the following error after starting from terminal:


/home/MYNAME/.local/share/Steam/steam.sh: line 161: VERSION_ID: unbound variable

/home/MYNAME/.local/share/Steam/steam.sh: line 161: VERSION_ID: unbound variable

Running Steam on arch  64-bit

/home/MYNAME/.local/share/Steam/steam.sh: line 161: VERSION_ID: unbound variable

STEAM_RUNTIME is enabled automatically

/home/MYNAME/.local/share/Steam/steam.sh: line 756: 11626 Segmentation fault      (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"

I've googled for the errors, and it looks like the segmentation fault at line 756 is a common issue, but there are various solutions, and I've tried several, with no luck. I've tried

  1. Removing the nvidia driver of my card, going back to nouveau (all the following actions were made with nouveau), reinstalling steam;
  2. Installing steam-libs and trying to run with STEAM_RUNTIME=0 (never neeeded it);
  3. Copiyng the libraries as suggested in Arch Wiki (https://wiki.archlinux.org/index.php/Steam#Native_runtime:_steam.sh_line_756_Segmentation_fault);
  4. Removing mesa and reinstalling it, with all dependencies (whew!)

Nothing worked, so I'm looking for help.

Thanks in advance.

SALVOuankeBALDO commented 8 years ago

I've solved the problem. I removed the folder /home/USER/.local/share/Steam, uninstalled steam (I do not think it is necessary, but I did it anyway) and reinstalled it. It asked me to reinstall that folder, and updated. Now it's working. I'm marking it as solved.

EDIT: I removed my local games, so this solution could not be optimal, as I have to donwload everything again. It is not an issue for me, but it would be nice to know exactly what to erase next time this issue happens.

ljrk0 commented 8 years ago

Remove everything except ~/.local/share/Steam/steamapps

Bfgeshka commented 8 years ago

There's no need to remove everything, config/config.vdf is enough. And ever more, seems like if you'll remove flag for remembering password at login screen steam wouldn't segfault anymore. At least works for me.

SALVOuankeBALDO commented 8 years ago

Thank you for your suggestions. Removing the "Remember password" flag should not help while the bug is happening, as I wasn't even able to reach the login screen. Steam crashed just after typing "steam" in the console. Now it's working fine, but next time I'll try your methods to solve it.

the-moose-machine commented 7 years ago

There's no need to remove everything, config/config.vdf is enough.

This was perfect. This is how i solved it on my 64-bit Arch Linux set-up:

First: $rm ~/.local/share/Steam/config/config.vdf

Second: Reinstall steam using pacman If you get the following prompt: select 'Y' :: lib32-libudev0-shim and lib32-libudev0 are in conflict. Remove lib32-libudev0? [y/N] y

Third: $steam-native

C0rn3j commented 7 years ago

In response to the command above - you need to install steam-native-runtime, not reinstall steam, as that doesn't help.

bkdwt commented 4 years ago

There's no need to remove everything, config/config.vdf is enough. And ever more, seems like if you'll remove flag for remembering password at login screen steam wouldn't segfault anymore. At least works for me.

Thank you very much! This works for me on Gentoo. Unfortunately having to enter the password every time you start the app is uncomfortable, but that's the way.

kiprasmel commented 4 years ago

For anyone else coming up here - my issue was solved here: https://github.com/ValveSoftware/steam-for-linux/issues/6399#issuecomment-512867551

I needed to

sudo pacman -S lib32-nvidia-utils

since I didn't have'em. Leggo!

auroraflux commented 4 years ago

For anyone else coming up here - my issue was solved here: #6399 (comment)

I needed to

sudo pacman -S lib32-nvidia-utils

since I didn't have'em. Leggo!

This worked for me (as the other stuff about the config.vdf didn't seem to apply to me because this file wasn't present on my system). I just wanted to chime in here since this is currently the top result on Google if you search for "steam.sh segmentation fault". Installing these utils is what worked.

Info about my setup:

I did not install any "native runtime". I'm using just the standard steam package.

robin-thoni commented 3 years ago

Removing the ConnectCache entry in config/config.vdf is enough, although it's just a WAR...

pueppiblue commented 3 years ago

Removing the ConnectCache entry in config/config.vdf is enough, although it's just a WAR...

Had the same problem on Ubuntu focal, after a steam update. Removing ConnectCache entry worked for me as well.

kisak-valve commented 3 years ago

Hello @robin-thoni, @pueppiblue, the issue you've described is being tracked at #6101 instead of this issue report.

me4real commented 3 years ago

Thank you for your suggestions. Removing the "Remember password" flag should not help while the bug is happening, as I wasn't even able to reach the login screen. Steam crashed just after typing "steam" in the console. Now it's working fine, but next time I'll try your methods to solve it.

Bro I'm having this issue. How did you solve it then?

GaussianWonder commented 2 years ago

This is an old git-issue post, probably nowadays some other problems can cause this behavior.

After a fresh linux reinstall of linux I started ricing my setup. In the process i had steam download some games I usually play. It worked, and it successfully launched games too. However, after a few more days of messing around with my setup, Steam was segfaulting at startup immediately after checksum validations. Whether or not this was a similar case to you, the following still applies:

In my specific scenario I messed up some cursor and font packages. After installing lib32-libxcursor lib32-fontconfig (arch) the issue was solved. I doubt this will specifically solve your problem, but you can check for such errors via coredumpctl gdb steam.

Other posts regarding this issue suggest