Steam client gets a segmentation fault (line 756) #4144
Comments
|
Hello @TacoDeBoss, if the steam client is working, please include your system information as requested at https://github.com/ValveSoftware/steam-for-linux#reporting-issues, especially any CrashIDs, or if it is not working, then upload the assert somewhere and share a link here. Can you test a while with the steam controller disconnected to see if your issue is #4129? |
|
Sure. Here's the output from Steam's System Information: And the CrashID: I tried disconnecting the Steam Controller, and the problem still persists. |
|
CrashID Changes each time. I just got |
|
@TacoDeBoss per a discussion earlier on an irc channel, did you also remove the steam controller wireless dongle when doing that test? |
|
@Tele42 Yes, the problem seems to occur regardless of a steam controller dongle being connected. |
|
You are not supposed to use the mainline kernel packages from Ubuntu's PPA as they are with any sort of out of tree modules such as the nvidia or virtualbox drivers. The correct way is to generate the kernel packages yourself. This will ensure that both the kernel and the out of tree modules were generated using the same gcc version. More info here: Guide to build generate your own packages here: Anyway I can reproduce this easily thanks to info on this thread: Basically, to get Steam to crash you just need to attempt to restore a game from a backup. You get a similar message to this: The crash does not happen if I revert to driver version 355.11 |
|
I can reproduce this on 64 bit Arch Linux with a GTX 660 and latest NVIDIA drivers. Steam crashes a lot even without any action on my side, possibly when receiving chat messages. This wasn't a problem with 355. |
|
Same here on Arch Linux with a GTX970, kernel 4.2.5 and nvidia 358.16. Crash ID: I can reproducibly trigger the crash by trying to assign a game to a category. I also have a Steam Controller adapter attached, but that seems to be unrelated as per above comments. |
|
It's been several days and I don't have this issue anymore unless I set a game's category. |
|
I have the same problem. Steam frequently crashes, sometimes without any sort of input on my part. Here's a log: A relevant CrashID, though not this specific one Relevant info: |
|
After reinstalling Linux Mint on my SSD, the issue is back. |
|
I have this issues as well Arch with Latest Nvid Drivers |
|
Same issue with Fedora 23 : |
|
I just installed Nvidia GTX970 on my computer to replace my previous AMD card and I'm having the same issue. Steam is practically unusable since it crashes after a while with no warning. Running Arch with kernel 4.2.5-1-ARCH x86_64. Using proprietary Nvidia drivers version 358.16. |
|
This has been mentioned in other simular issue reports, but I'll explicitly mention it here, there is a known issue with nvidia 358, but not 355. nVidia needs to fix their driver. |
|
Can someone please link to issue with Nvidia. |
|
I don't know of a proper issue tracker, but there is https://devtalk.nvidia.com/default/topic/899924/. |
|
I also got this problem since roughly a week. |
|
I've been facing a similar problem. Also getting these: the wrong elf class is there a hundred times or more. |
|
nvidia 361.18-1 is in the Arch Linux From the release notes (not sure if this is our bug):
|
|
I tried with nvidia 361.18-1 and still get a seg fault. Here is the gdb output: LDD on those files reports some libs "not found": I can't find any packages that own those files with pkgfile or searching the AUR - if they are the issue. My system information: |
|
I can confirm. Same issue here
|
|
Updating to nvidia-drivers-361.18 on gentoo seems to have solved the problem for me. Steam has been running since the 30th and usually it would have crashed by now, so it seems to be OK for now. |
|
Yes, the problem is with that particular version of nvidia drivers. I switched to the testing repos on Arch and the new version has fixed the issue. |
|
It's a pity there is no 361 package in Rpmfusion yet. Even for Rawhide. Will have to wait for it. |
|
Civilization V doesn't run with anything above 352.63 for me. Too bad too, the 361.18 fix a few KDE bugs, but I play Civilization almost daily while on my treadmill. |
|
nvidia 361.18 is now in stable repos on Arch Linux. I upgraded a few days ago; just got another segfault when launching Dota 2 on nvidia 361.18 / linux 4.4.1 now. |
|
I had to run "steam --reset" and then "STEAM_RUNTIME=0 steam" launched successfully. Re entered credentials, then enabled beta and restarted steam and it start OK. When I try to launch Big Picture Mode (to use steam controllers) or automatically start in Big Picture Mode, the original segmentation fault comes up "~/.local/share/Steam/steam.sh: line 756: 28526 Segmentation fault" Tried launching steam with both the controller usb dongle inserted and removed. Arch Linux 4.4.1-2 |
|
I've been running 361.18 drivers since they came out, and the issue no longer is present for me. |
|
Steam is crashing with same segfault with nvidia 361.28-1 on Arch Linux 4.4.1-2, but only when trying to launch big picture (after starting steam). |
|
I get this segfault CONSTANTLY. I'm running Void Linux, have had this segfault multiple times a day regardless of open beta or not. I just got a steam controller, too... It looks like it segfaults when it tries to run the Steam debugger, which makes me wonder if it's a missing debugger? |
|
I ran I suspect the people at Valve will have a better idea of what to do with this. |
|
Someone else explained a possible cause of the problem here: |
|
Running with glibc version 2.22 does not fix the problem. It would be nice to at least have some confirmation from Valve that this is being worked on. EDIT: DOWNGRADING GLIBC MAY BREAK YOUR SYSTEM. Don't learn this the hard way. |
|
Driver info: I'm...not sure why I have so many different versions of mesa installed. Pretty sure I don't have an ATI card, or if I do, it's masked by the intel chips. |
|
As of right now this problem still persists on Fedora 23 with the lastest kernel and nvidia drivers. Does anyone have a workaround other than booting in noveau? I've removed noveau and blacklisted it which is necessary for my configuration. |
|
This problem persists on arch 64 bit. Crash when launching steam big picture. |
|
It looks like this issue stems from running steam with When running Steam with its shipped runtime " |
|
Ok then, I had plenty of libc (and libudev) segfaults here while using fglrx (oddly they don't open with radeon driver), but finally I got the client starting with native libs. EDIT: yesterday update did nothing. |
|
Posting it here, since since this page pops out first when you try to google "steam 756 segmentation fault" |
|
Hello, the original issue tracked here appears to have been a regression in the nvidia 358.xx series driver, which is no longer supported. The other unrelated issues appear to due to the overly generic issue report title and should have been tracked separately. Closing as video driver quality from 2015 is no longer relevant. |
and others
Seemingly randomly, while using the Steam client, the client will crash with a Terminal output of:
assert_20151119062153_1.dmp[18659]: Uploading dump (out-of-process) /tmp/dumps/assert_20151119062153_1.dmp /home/taco/.local/share/Steam/steam.sh: line 756: 18483 Segmentation fault $STEAM_DEBUGGER "$STEAMROOT/$STEAMEXEPATH" "$@"Every time, the number before the words 'Segmentation fault' will change.
I've reinstalled after an
apt-get purge steam*, as well as a deletion of ~/.steam and ~/.local/Steam five or six times to no avail, as well as uninstalling Nvidia proprietary drivers and reinstalling the Steam client while using Nouveau drivers, as recommended in a forum thread I read.This error is happening on Linux Mint 17.2 Rafaela 64-bit XFCE (Ubuntu 14.04 LTS base with 4.1.7-040107-generic kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ ) with a GTX 780 Ti, Intel Core i7-3770k, 16 GB RAM. I have a Steam Controller, but this does not seem to be relevant.
This error is recent. (2-4 weeks ago this problem started)
On my other machines and operating systems this does not seem to happen.
The text was updated successfully, but these errors were encountered: