1 april 2026 update of Steam Linux Runtime 3.0 (sniper) casues Counter-Strike:Source to crash upon start (libc.so.6)

[Apachez-]

How it looks like when its crashing with the 1 april 2026 update of Steam Linux Runtime 3.0 (sniper):

apr 04 03:23:04 nuc steam[90220]: Adding process 91245 for gameID 240
apr 04 03:23:04 nuc kernel: cstrike_linux64[91246]: segfault at fffffffffffff720 ip 00007fae6e6d0031 sp 00007fff983b01c8 error 5 in libc.so.6[d0031,7fae6e628000+199000] likely on CPU 1 (core 1, socket 0)
apr 04 03:23:04 nuc kernel: Code: ff 0f 00 00 66 0f 60 c9 48 3d bf 0f 00 00 66 0f 60 d2 66 0f 61 c9 66 0f 61 d2 66 0f 70 c9 00 66 0f 70 d2 00 0f 87 ff 02 00 00 <f3> 0f 6f 1f 66 0f ef ed f3 0f 6f 67 01 66 0f 6f f3 66 0f 74 d9 66
apr 04 03:23:04 nuc steam[90220]: Adding process 91246 for gameID 240
apr 04 03:23:04 nuc steam[90220]: /home/<REMOVED>/.steam/steamapps/common/Counter-Strike Source/cstrike.sh: line 113: 91246 Segmentation fault      (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"
apr 04 03:23:05 nuc steam[90220]: Game Recording - game stopped [gameid=240]
apr 04 03:23:05 nuc steam[90220]: Removing process 91246 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91245 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91244 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91242 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91241 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91145 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91144 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91143 for gameID 240
apr 04 03:23:05 nuc steam[90220]: Removing process 91142 for gameID 240

Found a workaround when using Ubuntu 25.10 AMDv3:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 25.10
Release:	25.10
Codename:	questing

$ uname -a
Linux nuc 6.17.0-20-generic ValveSoftware/Source-1-Games#20-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 13 20:07:29 UTC 2026 x86_64 GNU/Linux

1. Go to Steam -> Library and rightclick on "Counter-Strike: Source" and select "Properties".

2. Make sure that for "Compatability" you have disabled "Force the use of a specific Steam Play compatiblity tool". This means that it will use the "Steam Linux Runtime 3.0 (sniper)" by default.

3. Press the "X" in the upper right of above dialog to close it.

4. Go to Steam -> Library and in the upper left click so you have both "Games" and "Tools" enabled as filter. Then rightclick on "Steam Linux Runtime 3.0 (sniper)" and select "Properties".

5. Then in "Game Versions & Betas" select "previous_release, Mar 17, 2026".

Now the game will start without libc.so.6 crashing.

[Apachez-]

Also this was crashing both with an empty "Launch Options" and with "Launch Options" set to:

LC_ALL=C PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -console -high -preload -noborder -noipx -nohltv -nojoy -nosteamcontroller -novid -NoQueuedPacketThread -enablefakeip -no_texture_stream -particles 512 -tickrate 128 +cl_updaterate 128 +cl_cmdrate 128 +rate 128000 +fps_max 60 +r_dynamic 0 +mat_specular 0 +cl_disablehtmlmotd 1 -gl -gl_enablesamplerobjects +mat_queue_mode 2

[smcv]

@slouken, could this perhaps be a regression with SDL 3.4.2 and sdl2-compat by default? That's one of the major changes in that update. It's unfortunate that nobody reported this while that version was in beta.

I'm a little surprised that CS:Source is using sniper - I thought the Source Engine 1 family of games were all stuck on scout.

[smcv]

@Apachez-, please try with the default or client_beta branch of sniper (not the previous release), and with CS:Source's Launch Options set to:

STEAM_COMPAT_RUNTIME_SDL2=classic %command%

If that helps, then we know that this is a regression involving SDL 3.4.2 and sdl2-compat. If not, then it must be something else.

[smcv]

@Apachez-, please also try these Launch Options, again with the default or client_beta branch of sniper (not the previous release):

SDL_VIDEODRIVER=x11 %command%

and if that helps, then we will know that this is related to the fact that SDL3 and sdl2-compat default to using native Wayland, rather than X11 via Xwayland like "classic" SDL2 did.

Description: Ubuntu 25.10

Are you using Ubuntu's default desktop environment, a customized GNOME session that uses Wayland by default? Or if not, what desktop environment are you using?

[smcv]

Also, if you see a crash dump ID logged to the terminal, the systemd Journal or in ~/.steam/steam/logs/, which would look something like this:

crash_20260407123456_1.dmp[855066]: Uploading dump (out-of-process) 
/tmp/dumps/crash_20260407123456_1.dmp
...
crash_20260407123456_1.dmp[855066]: Finished uploading minidump (out-of-process): success = yes 
crash_20260407123456_1.dmp[855066]: response: CrashID=bp-a5a5a5a5-a5a5-a5a5-a5a5-a5a5a5a5a5a5
crash_20260407123456_1.dmp[855066]: file ''/tmp/dumps/crash_20260407123456_1.dmp'', upload yes: ''CrashID=bp-a5a5a5a5-a5a5-a5a5-a5a5-a5a5a5a5a5a5' 

then the crash dump ID, which is bp-a5a5a5a5-a5a5-a5a5-a5a5-a5a5a5a5a5a5 in this example, is often useful information for Valve developers. Yours would be a different string of random letters and digits, but in the same format.

[smcv]

@Apachez-, are you still using the same hardware that was reported in ValveSoftware/Proton#8472, with an Intel HD Graphics 5000 (HSW GT3) integrated GPU?

If you are, then that is likely to be a relevant data point that might help a developer to reproduce the problem. Please provide some information about your system.

[Apachez-]

Yes I am, I have got myself a Steamdeck OLED but not put it into "production" yet :-)

So I tried this:

1. Revert "Steam Linux Runtime 3.0 (sniper)" from "previous_release, Mar 17, 2026" to "Default Public Version, Apr 1, 2026".

2. Try to start "Counter-Strike: Source" using current launch options:

LC_ALL=C PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -console -high -preload -noborder -noipx -nohltv -nojoy -nosteamcontroller -novid -NoQueuedPacketThread -enablefakeip -no_texture_stream -particles 512 -tickrate 128 +cl_updaterate 128 +cl_cmdrate 128 +rate 128000 +fps_max 60 +r_dynamic 0 +mat_specular 0 +cl_disablehtmlmotd 1 -gl -gl_enablesamplerobjects +mat_queue_mode 2

Result:

apr 08 16:21:47 nuc kernel: cstrike_linux64[1318790]: segfault at fffffffffffff720 ip 000079dbe88d0031 sp 00007ffc38694ef8 error 5 in libc.so.6[d0031,79dbe8828000+199000] likely on CPU 3 (core 1, socket 0)
apr 08 16:21:47 nuc kernel: Code: ff 0f 00 00 66 0f 60 c9 48 3d bf 0f 00 00 66 0f 60 d2 66 0f 61 c9 66 0f 61 d2 66 0f 70 c9 00 66 0f 70 d2 00 0f 87 ff 02 00 00 <f3> 0f 6f 1f 66 0f ef ed f3 0f 6f 67 01 66 0f 6f f3 66 0f 74 d9 66
apr 08 16:21:47 nuc steam[1314192]: /home/<REMOVED>/.steam/steamapps/common/Counter-Strike Source/cstrike.sh: line 113: 1318790 Segmentation fault      (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"

Similar result when I remove all launch options:

apr 08 16:23:22 nuc kernel: cstrike_linux64[1319265]: segfault at 0 ip 00007b1414798b0d sp 00007ffcd047dda8 error 4 in libc.so.6[198b0d,7b1414628000+199000] likely on CPU 1 (core 1, socket 0)
apr 08 16:23:22 nuc kernel: Code: 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 72 23 <c5> fe 6f 06 48 83 fa 40 0f 87 a5 00 00 00 c5 fe 6f 4c 16 e0 c5 fe
apr 08 16:23:23 nuc steam[1314192]: /home/<REMOVED>/.steam/steamapps/common/Counter-Strike Source/cstrike.sh: line 113: 1319265 Segmentation fault      (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"

3. Change launch options to:

STEAM_COMPAT_RUNTIME_SDL2=classic LC_ALL=C PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -console -high -preload -noborder -noipx -nohltv -nojoy -nosteamcontroller -novid -NoQueuedPacketThread -enablefakeip -no_texture_stream -particles 512 -tickrate 128 +cl_updaterate 128 +cl_cmdrate 128 +rate 128000 +fps_max 60 +r_dynamic 0 +mat_specular 0 +cl_disablehtmlmotd 1 -gl -gl_enablesamplerobjects +mat_queue_mode 2

Result:

It started now without crashing.

However when I remove all custom launch options except for the SDL2 stuff it crashes again:

STEAM_COMPAT_RUNTIME_SDL2=classic %command%

Result:

apr 08 16:28:57 nuc kernel: cstrike_linux64[1320964]: segfault at 0 ip 000079b65c398b0d sp 00007fff1f3459c8 error 4 in libc.so.6[198b0d,79b65c228000+199000] likely on CPU 2 (core 0, socket 0)
apr 08 16:28:57 nuc kernel: Code: 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 72 23 <c5> fe 6f 06 48 83 fa 40 0f 87 a5 00 00 00 c5 fe 6f 4c 16 e0 c5 fe
apr 08 16:28:58 nuc steam[1314192]: /home/<REMOVED>/.steam/steamapps/common/Counter-Strike Source/cstrike.sh: line 113: 1320964 Segmentation fault      (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"

4. Change launch options to:

SDL_VIDEODRIVER=x11 LC_ALL=C PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command% -console -high -preload -noborder -noipx -nohltv -nojoy -nosteamcontroller -novid -NoQueuedPacketThread -enablefakeip -no_texture_stream -particles 512 -tickrate 128 +cl_updaterate 128 +cl_cmdrate 128 +rate 128000 +fps_max 60 +r_dynamic 0 +mat_specular 0 +cl_disablehtmlmotd 1 -gl -gl_enablesamplerobjects +mat_queue_mode 2

Result:

It started now without crashing.

However when I remove all custom launch options except for the SDL2 stuff it crashes again:

SDL_VIDEODRIVER=x11 %command%

Result:

apr 08 16:33:06 nuc kernel: cstrike_linux64[1322186]: segfault at 0 ip 0000721bfbd98b0d sp 00007fff761e5638 error 4 in libc.so.6[198b0d,721bfbc28000+199000] likely on CPU 2 (core 0, socket 0)
apr 08 16:33:06 nuc kernel: Code: 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 66 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 83 fa 20 72 23 <c5> fe 6f 06 48 83 fa 40 0f 87 a5 00 00 00 c5 fe 6f 4c 16 e0 c5 fe
apr 08 16:33:06 nuc steam[1314192]: /home/<REMOVED>/.steam/steamapps/common/Counter-Strike Source/cstrike.sh: line 113: 1322186 Segmentation fault      (core dumped) ${GAME_DEBUGGER} "${GAMEROOT}"/${GAMEEXE} "$@"

Worth mentioning this is an Intel NUC D54250WY using Intel(R) Core(TM) i5-4250U CPU aka Haswell meaning it got Vulkan but broken from Valve point of view so I have to force it to run with -gl etc previously in order to not crash upon start.

Minimal launch options needed to not crash upon start:

STEAM_COMPAT_RUNTIME_SDL2=classic %command% -gl

or:

SDL_VIDEODRIVER=x11 %command% -gl

Output from System Information in Steam which might answer some of your Ubuntu-related questions?

Computer Information:
Manufacturer: Intel Corporation
Model: D54250WYK
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: GenuineIntel
CPU Brand: Intel(R) Core(TM) i5-4250U CPU @ 1.30GHz
CPU Family: 0x6
CPU Model: 0x45
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 2600 MHz
4 logical processors
2 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Unsupported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported

Operating System:
Ubuntu 25.10 (64 bit)
Kernel Name: Linux
Kernel Version: 6.17.0-20-generic
X Server Vendor: The X.Org Foundation
X Server Release: 12401006
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime_1.0.20260316.216267

Client Information:
Version: 1775605734
Browser GPU Acceleration Status: Disabled
Browser Canvas: Unavailable
Browser Canvas out-of-process rasterization: Disabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Disabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Disabled
Browser Rasterization: Disabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Disabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Unavailable
Browser WebGL2: Unavailable
Browser WebGPU: Disabled
Browser WebNN: Disabled

Video Card:
Driver: Intel Mesa Intel(R) HD Graphics 5000 (HSW GT3)
Driver Version: 4.6 (Compatibility Profile) Mesa 25.2.8-0ubuntu0.25.10.1
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 59 Hz
VendorID: 0x8086
DeviceID: 0xa26
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1680 x 1050
Desktop Resolution: 1680 x 1050
Primary Display Size: 18.90" x 11.81" (22.28" diag), 48.0cm x 30.0cm (56.6cm diag)
Primary VRAM Not Detected

Sound card:
Audio device: Realtek ALC283

Memory:
RAM: 15375 Mb

VR Hardware:
VR Headset: None detected
No VR configuration with trackers detected
Most number of trackers in a session: 0

Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 938508 MB
Largest Free Hard Disk Block: 87975 MB

Storage:
Number of SSDs: 1
SSD sizes: 1024G
Number of HDDs: 0
Number of removable drives: 0

[smcv]

Worth mentioning this is an Intel NUC D54250WY using Intel(R) Core(TM) i5-4250U CPU aka Haswell meaning it got Vulkan but broken from Valve point of view so I have to force it to run with -gl etc previously in order to not crash upon start.

Right, the Haswell-era integrated GPUs are just not enough GPU to provide the Vulkan features that TF2 wants. So I think that's consistent with you needing to use -gl as a workaround for that.

The rest of your custom launch options I don't know whether they're helping you, hurting you, or not doing anything either way - but because you've been able to narrow down a minimal working configuration, we don't need to think about those from the runtime's point of view.

Minimal launch options needed to not crash upon start: STEAM_COMPAT_RUNTIME_SDL2=classic %command% -gl or SDL_VIDEODRIVER=x11 %command% -gl

OK, good. We now think that we mostly understand what is going on, so the next Steam Runtime beta should reduce those down to just %command% -gl for your older GPU.

For now, I'd suggest that you use SDL_VIDEODRIVER=x11 %command% -gl (plus whatever other options you feel are necessary) which is the less intrusive workaround.

PROTON_FORCE_LARGE_ADDRESS_AWARE=1

FYI, this does absolutely nothing for native Linux games, unless something extremely strange is happening. It's only relevant when running Windows games under Proton.

[Apachez-]

Thanks!

I will await a new beta of "Steam Linux Runtime 3.0 (sniper)" and test that once it arrives.

For now I use these launch options which works successfully for Counter-Strike: Source:

LC_ALL=C PROTON_FORCE_LARGE_ADDRESS_AWARE=1 SDL_VIDEODRIVER=x11 %command% -console -high -preload -noborder -noipx -nohltv -nojoy -nosteamcontroller -novid -NoQueuedPacketThread -enablefakeip -no_texture_stream -particles 512 -tickrate 128 +cl_updaterate 128 +cl_cmdrate 128 +rate 128000 +fps_max 60 +r_dynamic 0 +mat_specular 0 +cl_disablehtmlmotd 1 -gl -gl_enablesamplerobjects +mat_queue_mode 2

or minimal for this support case:

SDL_VIDEODRIVER=x11 %command% -gl

According to https://developer.valvesoftware.com/wiki/Command_line_options adding "-gl_enablesamplerobjects" might be preferred:

SDL_VIDEODRIVER=x11 %command% -gl -gl_enablesamplerobjects

Some of the options for my longer launch options are workarounds and performance options.

Also some might not be needed any longer but I use the same launch options for all my games no matter if they are native Linux or not.

PROTON_FORCE_LARGE_ADDRESS_AWARE=1

Some old workaround, I think related to Trackmania and as you said Windows games running in Linux (aka not Linux native). Worth mentioning if I manually change which Proton version to use then Proton 7.0-6 is the latest one that works without issues. It could be that the fix where this option is no longer needed exists in newer Proton versions.

+fps_max 60

The box is passively cooled and the monitor is 60Hz so no need to use more CPU than needed.

+r_dynamic 0 +mat_specular 0

Some older workaround where Haswell had issues with dynamic lightning (might be fixed today). I think the issue was heavy FPS drop.

-gl -gl_enablesamplerobjects

To force using OpenGL instead of Vulkan since Vulkan became the default even for older games (such as Counter-Strike: Source). Without this the game will crash on start.

+mat_queue_mode 2

A recent workaround for crashes ingame due to matqueue0.

Remaining issues/regressions (but will be handled in other threads/posts):

1. Waiting for Valve to include the fix for source SDK presented in:

ValveSoftware/Source-1-Games#6868

2. Every now and then game crashes when playing due to (seems to be related to specific servers or maps):

apr 08 17:06:10 nuc kernel: traps: cstrike_linux64[1330401] general protection fault ip:7b8cec35b3c5 sp:7fffce1a4b90 error:0 in libmimalloc.so[103c5,7b8cec351000+10000]

[Apachez-]

I have now received an update for my "Steam Linux Runtime 3.0 (sniper)" dated Apr 10, 2026:

Default Public Version
Most common version of the game
Apr 10, 2026

client_beta
use with Steam beta client
Apr 1, 2026

previous_release
previous release
Mar 17, 2026

I have the "Default Public Version" dated Apr 10, 2026 selected.

I can now start Counter-Strike: Source (Default Public Version dated Feb 18, 2025) without crashing both with and without the workaround of:

SDL_VIDEODRIVER=x11