I'm seeing a similar error but cannot start Steam at all. My client checks for updates a few times and then eventually dies with '/home/user/.local/share/Steam/steam.sh: line 713: 14663 Segmentation fault $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"'
I've tried resetting steam. I am opted into the Steam client beta. Steam client version: 1475701795. Distribution: Gentoo System is up to date.
@mmirg segmentation fault is happening at a different point it seems, but Ubuntu 16.04 at least in my case is having 5235 segmentation fault. One thing I have noticed it seems to be related to window activity, if I don't interact with mine after it starts it seems fine...
I have the segmentation fault problem on an Acer Aspire E5-574-59H5 with up to date Fedora 24 KDE. It is my first start after installing steam via dnf and it dies with "/home/user/.local/share/Steam/steam.sh: line 713: 2921 Segmentation fault". Every time i try to start steam, the seg fault code changes.
Maybe it is related to the X error some lines above? Full command line output see gist: https://gist.github.com/Harry-R/a1b6a400c7880a3259b9a5ae4046dd47
I am also getting this on Gentoo, up to date system and using up to date steam runtime. It initially crashes when logging in, directly after submitting login info and submitting steam guard code.
After clearing all local steam files, disabling steam guard, and unchecking remember password (and yes, it only worked after doing all three of those at the same time), it launched successfully one time, and promptly crashed again when launching a game. Now it will still crash on login, even with steam guard and remember password disabled.
I get something like this after each crash in stdout:
assert_20161028012157_1.dmp[6139]: Uploading dump (out-of-process)
/tmp/dumps/assert_20161028012157_1.dmp
/home/daboross/.local/share/Steam/steam.sh: line 713: 6094 Segmentation fault $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"
assert_20161028012157_1.dmp[6139]: Finished uploading minidump (out-of-process): success = yes
assert_20161028012157_1.dmp[6139]: response: CrashID=bp-989984d8-5857-4a26-859d-5331a2161028
assert_20161028012157_1.dmp[6139]: file ''/tmp/dumps/assert_20161028012157_1.dmp'', upload yes: ''CrashID=bp-989984d8-5857-4a26-859d-5331a2161028''
The number in the [] changes each time - I think this is still the same crash others are experiencing. I can upload my .dmp files if that would be helpful.
Happening on Antergos (Arch based) x64.
Turns out that adding LD_PRELOAD=/usr/lib32/libudev.so.1 and starting it without steam-runtime will "fix" it on Arch-based distri (and possibly others as well).
As in, LD_PRELOAD=/usr/lib32/libudev.so.1 STEAM_RUNTIME=0 steam
Well, it will actually not be able to load that correctly, but it will run anyway.
Hello @Xiuhquiauitl, per https://wiki.archlinux.org/index.php/Steam/Troubleshooting#Libraries_for_x86_64 you should be using (lib32-)libudev0-shim with steam on Arch when the steam runtime is disabled instead of forcing the slightly ABI-incompatible libudev.so.1. Gentoo does something similar.
Oh, I see. I had the one without "shim". Well, thanks for the intel, going to try that.
Also getting this on Arch. Not sure if the LD_PRELOAD suggested above fixes it, but will try. Seems to happen whenever I leave Steam on and my PC goes idle (monitor turns off). Disabling steam runtime doesn't seem to solve it.
Hello, is anyone still experiencing this issue on an up to date system?
Closing pending feedback.
Nothing extracted yet.
Your system information
Please describe your issue in as much detail as possible:
I start Steam, and leave it running for extended periods idle, it shouldn't exit on it's own after 30~90 minutes. I can see that it actually has segmentation faulted
'/datastore/home/fang64/.local/share/Steam/steam.sh: line 713: 5235 Segmentation fault (core dumped) $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"'
fang64_stdout.txt log
Steps for reproducing this issue: