Steam crashes with various Valve titles if run from a user with 16 or more characters

[OJezu]

Your system information

• Steam client version (build number or date): 1504757234
• Distribution (e.g. Ubuntu): Debian 9
• Opted into Steam client beta?: [Yes/No] both
• Have you checked for system updates?: [Yes/No] yes

Please describe your issue in as much detail as possible:

Steam start-ups as usual, I start counter-strike, and Steam window closes (crashes with buffer overflow), 2 of 3 times Counter-Strike also crashes at this point. If not, it will crash when trying to create server (after setting game options), or when trying to view server list (on clicking Find Servers)

I've tried completely removing Steam (including ~/.steam directory) and i368 libs and reinstalling everything from scratch.

I've installed other game, FTL, and it seems to work fine, steam not crashing. Counter-Strike CZ is crashing itself and steam in same way as Counter-Strike (I didn't check logs for that though).

System was recently upgraded from Debian 8. Before that update Counter-Strike worked fine.

uname: Linux hostname 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u3 (2017-08-06) x86_64 GNU/Linux

processor: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz

graphic adapter: Intel Corporation HD Graphics 5500

Steam console output and system information: https://gist.github.com/OJezu/feb8d6829633d60fee423f9a2119ea8a

Steps for reproducing this issue:

1. Start Counter-Strike
2. Steam crashes
3. If Counter-Strike did not crash at step 2, try viewing the server list or starting a new server, and it will crash

[kisak-valve]

Hello @OJezu, please copy your system information from steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report. In particular, if you can find any CrashIDs or minidumps related to this issue, please include them.

[OJezu]

@kisak-valve I added system information to already existing gist linked in issue.

And here are the dumps: steam-cs-dumps.tar.gz

[kisak-valve]

I gave this a try on my Debian 9 test box and could not reproduce the issue. My test box is using nvidia 340.102, so a mesa system may be needed to reproduce this issue. Possibly unrelated, but can you list the files found in ~/.steam/ubuntu12_32/steam-runtime/pinned_libs_32?

[OJezu]

@kisak-valve pinned_libs_32 is empty

$ ls -l ~/.steam/ubuntu12_32/steam-runtime/pinned_libs_32
total 0

[OJezu]

The crash is very strange, as it seems that Steam client crashes first, and then Counter-Strike quits on failed attempt to communicate with Steam (errors after command prompt in output). On the other hand, Steam does not crash on non-hl game. Maybe it is something with game state detection (like server I'm playing on?) I will see what happens, when I try to run CS:GO.

[OJezu]

When launching CS:GO Steam also crashed, but this time a nice error popup appeared. Once before the client window closed, and second time after the client already disappeared.

https://gist.github.com/OJezu/fb44feaacf4e5404179d776295556d60

[kisak-valve]

From #5162, this is not OS or driver specific.

[OJezu]

It's nice to see it confirmed, nonetheless, I think the new title is a bit misleading. The reason of Steam Client crash seems to be the buffer overflow as seen in both reports. Crash, or rather exit on assertion, of the game on "failed to connect" is a side-effect of game trying to connect to no longer existing Steam Client process.

*** buffer overflow detected ***: /home/reporter_name/.local/share/Steam/ubuntu12_32/steam terminated
======= Backtrace: =========
/usr/lib32/libc.so.6(+0x6a5e0)[0xf722c5e0]
/usr/lib32/libc.so.6(__fortify_fail+0x38)[0xf72c0ec8]
/usr/lib32/libc.so.6(+0xfd0f8)[0xf72bf0f8]
/usr/lib32/libc.so.6(__strncat_chk+0x39)[0xf72be709]
[0xeeda2dfd]
[0x0]

[kisak-valve]

Got a better suggestion that is easily search-able?

[OJezu]

I've taken liberty to add "due to buffer overflow" to the title. "Buffer overflow" might be something people look for when experiencing the issue.

Alternative would be "Steam crashes with buffer overflow, game crashes with Failed to connect with local Steam Client process"

[headlesscyborg]

I found out that it works if Steam is started in offline mode. Official servers and matchmaking in CSGO, TF2 and Dota 2 is still unavailable but community servers (CSGO/TF2) work. It might be a workaround for someone who wants to play on community servers meantime.

[CuriousTommy]

Steam does not crash on non-hl game. Maybe it is something with game state detection (like server I'm playing on?) I will see what happens, when I try to run CS:GO.

Yeah, I noticed that the bug seems to affect certain Valve games. However, Portal 2 does not seem to be affected while L4D2, TF2, and HL are.

There was also a case where Steam would crash when I run Sanctum 2 or Payday 2 (and the game would not launch either). It doesn't seem to happen anymore though.

[mikupandi]

Still without solution for this issue?.

[headlesscyborg]

Any workaround or a solution? Should I install Steam in Wine after 5 years without Wine/Windows? It looks like it won't be fixed anytime soon.

[mikupandi]

@thedarkfighter413 I'll hope for a solution, but devs don't say any since last message. In the meantime, more people are experiment the same trouble.

[ghost]

I've been experiencing the same issue on Arch, none of the games in my library work. I'm wondering who this affects, most of those who I ask that run various Linux distros still have a working Steam.

[zpostfacto]

Do you have a dump file you can send to us? EDIT: Just saw the post where you attached some dumps.

[headlesscyborg]

I know this comment won't add anything to the discussion and maybe it's against the rules but I have to ask - are you working on it? I would say it is something that should be fixed ASAP with higher priority but it looks like nobody cares. I am forced to use Windows and it is an incredibly painful experience.

Btw. I tried installing Ubuntu on my second ssd and it doesn't work either so supported distributions are affected as well.

[headlesscyborg]

Workaround: 1) Start Steam in online mode 2) Start a game 3) Immediately unplug your ethernet cable (or turn off wi-fi) 4) As soon as the game starts you have to plug back your ethernet cable (or turn on wi-fi, seriously ASAP) 5) Access your in-game inventory to let the game connect to the servers 6) Done. It works with TF2, CSGO and Dota 2 - https://youtu.be/WI3C-Bnkcwc

Edit - ok, it works only for TF2. But it's better than nothing so at least we can play TF2 until the issue gets fixed in the year 2035.

[mikupandi]

@thedarkfighter413 This doesn't work with Dota 2. It was stuck in: 'searching for the Dota 2 game coordinator.' and when getting to load, Valve anti cheat was activated or crashed again.

[mikupandi]

Wow 11 days and we don't have any solution.

[FirstTimeInForever]

Same issue on KUbuntu 17.04 when trying to start Dota 2. uname: Linux 4.10.0-35-lowlatency #39-Ubuntu SMP PREEMPT Wed Sep 13 09:18:37 UTC 2017 x86_64 dumps.zip steam output

[thekingofravens]

Can confirm this in arch linux with either native or steam runtime. EDIT: To clarify, I mean that both are affected.

[CuriousTommy]

@deathbyfreezeray I am running Arch Linux on my desktop. I know for sure that Steam runtime is affected. Not sure about the native version.

[headlesscyborg]

Still no answer - Valve could you please give us an update about the status of this issue? I want to believe you are working on it but it looks like nobody cares and meantime more and more people are affected - #5168

EDIT 4 days later - I don't want to be rude or ungrateful but seriously if you call this customer support then I have literally no reason to buy a game on Steam anymore if it takes almost a month to fix an issue like this with no chance to get an answer if you are working on a solution. Sorry, I am just honest.

[OJezu]

@fletcherdvalve Do you need any additional assistance (or information) in recreating the issue?

[mikupandi]

@fletcherdvalve Still without any solution, are you sure that don't need more assistance information?. We've waited around one month.

[thekingofravens]

I should mention that I am also using an nvidia based system but with the newest driver (384.69) and kernel mode setting enabled. This is not a mesa bug. Especially given the behavior of the weird network disconnect workaround that sometimes works.

Linux Nerdbox-XII-Linux 4.12.13-1-ARCH #1 SMP PREEMPT Fri Sep 15 06:36:43 UTC 2017 x86_64 GNU/Linux

AMD® Ryzen 3 1200 quad-core processor × 4

GeForce GTX 1050 Ti/PCIe/SSE2 (384.69)

[headlesscyborg]

14 days passed and still no answer. So here is my question again: are you working on it? Any chance we will get an answer before the end of this year?

I am not mad because it's not fixed yet. I am mad because nobody cares about my question. I think it would be fair to say something like "we are working on it" or "the issue has nothing to do with Steam, new version of mesa/nvidia driver/library XYZ... should fix it..." etc. It's a shame.

[andersonzanichelli]

Only us having this problem? I don't believe!

[andersonzanichelli]

WTHack! kkkk

Following these instructions the game works:

thedarkfighter413 commented 13 days ago • edited Workaround:

Start Steam in online mode Start a game Immediately unplug your ethernet cable (or turn off wi-fi) As soon as the game starts you have to plug back your ethernet cable (or turn on wi-fi, seriously ASAP) Access your in-game inventory to let the game connect to the servers

[FirstTimeInForever]

I installed Fedora 26 to other partition and it had same issue. I was trying to start Factorio and steam crashed with the same error. I swapped Fedora with Ubuntu Gnome and had exactly the same issue. There are a lot of people here waiting for the fix. I hope this issue will be fixed as soon as possible.

[andersonzanichelli]

Oh, don't work perfectly =(

[headlesscyborg]

@andersonzanichelli It works with inventory items as well if you wait a minute or two but only on community servers. It says "VAC could not verify your session". Another workaround for this is to disconnect and reconnect network again (in menu), then it says "searching" forever. The only playable game using this workaround is TF2 (inventory and even matchmaking works).

I also tried replacing Network Manager with Wicd but it didn't help. Disabling NetworkManager.service also didn't help. And "unshare" command (limiting network connection for Steam) also with no success. Dualboot with Ubuntu 17.10 daily build - the same problem.

[Aherin]

hedarkfighter413 commented 13 days ago • edited Workaround:

Start Steam in online mode Start a game Immediately unplug your ethernet cable (or turn off wi-fi) As soon as the game starts you have to plug back your ethernet cable (or turn on wi-fi, seriously ASAP) Access your in-game inventory to let the game connect to the servers

This works just one time.....still have the same issue.

[headlesscyborg]

So here is official Steam support response about this problem.

**Since Linux is built by each user from an open source there is just no possible way to offer software that is going to be compatible out of the box with the entire spectrum of builds. As a Linux user, you should be prepared to craft your operating system to accommodate the software.

We are glad to look at the details and offer direction, but your primary resource is going to be yourself along with the online communities working with similar software.

Regards,
Sterling**

Ok. I am done. CSGO, TF2 and Dota 2 uninstalled.

[thekingofravens]

The complete lack of concern is disturbing. Valve isn't exactly known for customer service, PR, or caring about people in general however. Therefore, I am sure it will get fixed eventually, just not in a reasonable time frame.

[thekingofravens]

Here is all the information I can offer:

Steam client version: 1506500000 Distribution: Arch Linux Opted into Steam Beta: Both Checked for System Updates: Yes

uname -a: Linux Nerdbox-XII-Linux 4.13.3-1-ARCH #1 SMP PREEMPT Thu Sep 21 20:33:16 CEST 2017 x86_64 GNU/Linux

All of the different dumps steam made from one launch: dumps.zip

all other information is in a gist

[kisak-valve]

For reference, in the attached minidumps, crash_20171001045707_1.dmp is a SIGABRT in linux-gate.so and the rest are DUMP_REQUESTED in crashhandler.so.

[FirstTimeInForever]

So, I did a clean install of kubuntu 17.04. Installed steam with apt. Installed Factorio game - and it worked! That is strange, because last time I tried - steam crashed as usual. Now I'll try to install dota 2 and see if it will break steam or not (my guess is that it somehow breaks steam and other games).

[FirstTimeInForever]

I installed dota 2 and now steam crashes again. Same error. fresh steam output fresh dumps.zip steam info uname -a : Linux lambsauce 4.10.0-35-lowlatency #39-Ubuntu SMP PREEMPT Wed Sep 13 09:18:37 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

[John-Gee]

Looking at 2 outputs, the backtrace was always about glibc 32b, I wonder if you guys got a glibc upgrade that broke your setup. Maybe it only causes problems with certain CPUs and not others... 2.26 was released mid-August which could is close to the opening date of this.

[FirstTimeInForever]

@John-Gee Someone pointed out that there is a bug in glibc 2.24, that is fixed in 2.26. So now I am trying to get 2.26 to test.

[headlesscyborg]

@John-Gee I just tried downgrading my glibc packages from 2.26 to 2.25 (glibc-2.25-2-x86_64.pkg.tar.xz and lib32-glibc-2.25-3-x86_64.pkg.tar.xz) and the problem persists. By the way thank you very much for replying and let us know if we can do anything to help. It is nice to know that we are not left forgotten.

[John-Gee]

I don't work for Valve, so don't think much of my guesses :)

Running the whole thing through gdb might show more.

[headlesscyborg]

@John-Gee Sorry I thought you are a Valve employee because my brain was focused on downgrading glibc packages. By the way - reinstallation didn't help. Yes I had to reinstall my OS because I screwed up my system by trying to downgrade glibc to a version from June 2016. So I am now on a fresh Arch Linux installation and the problem still persists.

[FirstTimeInForever]

Same error with libc6: 2.26-0ubuntu1.

[Aherin]

Console output when dota 2 play button is pressed

[thekingofravens]

Attempting to reproduce the issue in VirtualBox with 3d acceleration enabled I cannot reproduce it with ubuntu 17.04 64-bit, Dota 2 installs and launches perfectly with the latest updates installed. Testing with a fresh install Arch Linux VM, same results. Dota 2 runs perfectly in both steam and native runtimes.

To me this leaves two guesses (please note this is just speculation):

1. A hardware configuration/driver related issue
2. An upgrade issue related to upgrading software to a newer version.

[thekingofravens]

Doing more tests, I tried reinstalling my actual system with arch linux, doing it in place (I did not erase /home). The issue persists. This leaves me to believe this is probably a hardware/driver specific issue. Except there is such a wide variance between my hardware and that of the OP. So its honestly hard to tell