Half-Life: Alyx is CRASHING on Linux in a VERY specific way. THREE players on Valve’s own SteamVR for Linux issue tracker report that the game’s NATIVE Linux build exits when a barnacle is shot and its blood spray FILLS the view. All three were playing on a STEAM FRAME. As of the evening of October 4, 2026, Valve had posted NO reply on the report, and no FIX is attached to it.
What the Reports Say
The opening report, issue #983, was FILED on October 3 by GitHub user jonkoops. “The native Linux build of Half-Life: Alyx crashes when a barnacle is shot and the blood spray fills the view,” it reads. “The hlvr process disconnects from SteamVR. This happens almost every time that spray fills the view.” That machine RUNS CachyOS with an AMD Radeon RX 9070 XT on Mesa 26.2.4, with a Steam Frame and Frame controllers. The reporter says the crash ALSO reproduces on the Steam client beta, the SteamVR beta and SteamOS Preview on the headset. That is the SAME beta track Valve has been pointing Frame owners toward for its Error 17 streaming fault.
A SECOND account, on an NVIDIA RTX 3090 running Arch Linux, posted a MATCHING exit after a grenade BLEW UP a barnacle. The trace shows a SIGSEGV in a libscenesystem.so worker thread with NO GPU driver frames in the stack. That user’s WORKAROUND is to force Proton Experimental. They report two sessions of about 19 and 13 minutes under Proton WITHOUT a crash, but they say they had not specifically retested a barnacle kill there.
A THIRD reproduction, on an RTX 4080 under Linux Mint 22.3 with the SteamVR 2.18.2 beta, comes with PER-SECOND counters. In the SECOND the game died, the hlvr process grew by 72.4 MB, GPU use JUMPED from 59% to 99%, and die temperature rose 9°C. Two EARLIER barnacle kills in the same session SURVIVED. Their largest one-second jump was 18.1 MB, and that memory was RELEASED IMMEDIATELY afterward. The reporter RULES OUT thermal or power THROTTLING: the clock held at 2,790 MHz and peak draw was 231 W against a 320 W limit.
Valve’s Only Reply Was to a Different Crash
Valve did respond to ONE Alyx report this weekend, but NOT this one. On October 4 at 12:44 UTC, the kisak-valve account, which GitHub lists as a member of Valve’s organization, closed issue #986. That report describes a DETERMINISTIC fatal assertion in the game’s entity serialization code during the a2_pistol train ride. “This issue is already being tracked in several issues like #405 / #784 / #801,” the reply reads. “Closing as a duplicate.” A duplicate closure is NOT a fix. The oldest of those tracking issues, #405, was opened on November 9, 2020 and is STILL OPEN, nearly SIX years later.
MIXED first CONNECTED the two threads and notes that Alyx LED Steam’s VR-only sales chart on October 4. That makes the timing AWKWARD for Valve’s Linux-first HEADSET push.
What This Does and Does Not Prove
The reports do NOT pin the bug on the Steam Frame, even though EVERY reporter uses one. They span TWO GPU vendors and two driver stacks, and the traces carry NO driver frames. The common factor is the native Linux BINARY, not the HEADSET. One commenter floated the idea that the full-view spray is costly to ENCODE and overloads the stream, but that is a GUESS, not a FINDING. There is also no SCALE here: NOBODY has published how many owners hit the crash. Two users SEPARATELY report audio CRACKLING that appears ONLY in the native Alyx build.
For now, the PRACTICAL path for Linux players is the one the second reporter took: run Alyx through PROTON rather than the native build, and WATCH issue #983 for a Valve RESPONSE. Until Valve COMMENTS, treat the native Linux build as UNSTABLE in barnacle-heavy areas.
Sources: ValveSoftware/SteamVR-for-Linux issues #983, #986 and #405 (read October 4, 2026); MIXED (Chris Steven, October 5, 2026); Half-Life: Alyx on Steam.