Open telephrag opened 11 months ago
any update on this? i'm having the same issue, and by playing around with the cs2.sh file i discoverd that the STEAM_RUNTIME_PREFIX at line 115 it's empty, and doesn't get set early in the script, and i thought it was what it was causing the segmentation fault
but even by forcing the value in the script it doesn't work, it just hangs for a couples seconds before crashing again
any update on this? i'm having the same issue, and by playing around with the cs2.sh file i discoverd that the STEAM_RUNTIME_PREFIX at line 115 it's empty, and doesn't get set early in the script, and i thought it was what it was causing the segmentation fault
but even by forcing the value in the script it doesn't work, it just hangs for a couples seconds before crashing again
Nope
I am also seeing segfault in cs2 in loading screen, but seems to not affect all maps. I can play Vertigo and Dust2 just fine... All other maps I have tried segfault in loading screen. I am using amdgpu.
@telephrag have you figured out a quick fix?
i noticed that even after starting just the binary of cs (still using the steam runtime) that it says that i'm missing a dynamic library (libcurl.so), but even after adding it in the folder it still says it like nothing change :(
@telephrag have you figured out a quick fix?
i noticed that even after starting just the binary of cs (still using the steam runtime) that it says that i'm missing a dynamic library (libcurl.so), but even after adding it in the folder it still says it like nothing change :(
Haven't tried anything yet. Gonna be trying to launch it with different main menu background map since, @esiqveland stated that the crash is map specific on his machine.
@gasbytes @esiqveland I'm thinking that issue might be libc
related. Is anyone of you running musl libc
based distro like I do?
I do not run on musl libc. However, it seems to be working for me since the update on Thursday, but its a bit scary to try competitive while I am not sure it will segfault in loading screen again :smiley:
@telephrag nope, i run glibc, and yes the error it is libc related
the cs client doesn't even start in my case, it just goes straight to segmentation fault from the start, but it might be related to the background map who knows tbh since it's not easily debuggable
@telephrag I have a similar setup (Alpine Linux + sway) and I got the game to launch by switching to XFCE. I'm not sure what part of the Wayland stack is to blame, but I'm guessing either Xwayland or wlroots since the issue affects both sway and river.
Your system information
Please describe your issue in as much detail as possible:
I've launched the game from Steam and waited for shader compilation to complete. Then, the game just refused to launch while Steam logs were the following:
Edit:
libgtk-3.so.0
that is mentioned in the log is located at/home/telephrag/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/sniper_platform_0.20230919.60634/files/lib/x86_64-linux-gnu
on my system and calledlibgtk-3.so.0.2404.20
.Steps for reproducing this issue:
Edit: Updated the log to be more complete.