Half-Life: Alyx keeps crashing on Linux, and Valve's duplicate trail runs to 2020
Half-Life: Alyx's native Linux build exits when a barnacle is shot and the blood spray fills the view, according to reports from three accounts on Valve's own SteamVR for Linux tracker, two of them on Nvidia cards and one on AMD. The first report, issue #983, was opened on October 3 and was still open with no Valve reply when read at 23:44 UTC on October 4.

Half-Life: Alyx led Steam's VR-only sales chart on October 4. On Linux it has both a native build and a Proton route, and the crash reports concern the native one. Image: Valve
"The native Linux build of Half-Life: Alyx crashes when a barnacle is shot and the blood spray fills the view," the opening report says. "The hlvr process disconnects from SteamVR. This happens almost every time that spray fills the view." That reporter is on a Radeon RX 9070 XT with Mesa 26.2.4, driving a Steam Frame, and the game is the one that sat at the head of Steam's VR-only sales chart on October 4.
A second account reported the same exit on an Nvidia RTX 3090, with a SIGSEGV in a libscenesystem.so worker thread and no GPU driver frames in the stack. A third, on an RTX 4080 and Linux Mint, posted per-second counters showing the hlvr process allocating 72.4MB and the GPU jumping from 59% to 99% in the second it died.
Valve's only reply closed a different Alyx crash
On October 4 at 12:44 UTC the kisak-valve account, which GitHub lists as a member of Valve's organisation, closed a separate Alyx report, issue #986. "This issue is already being tracked in several issues like #405 / #784 / #801," it reads. "Closing as a duplicate."
That is a duplicate closure, not a fix, and not a response to the barnacle crash at all. Issue #986 describes a different failure with a different signature: a fatal assertion in the game's entity serialisation code during the train ride on the a2_pistol map, hitting the same bit offset on two crashes nine days apart from one autosave.
The three issues Valve's reply pointed at were all still open when checked at 23:44 UTC on October 4. Issue #405, on SteamVR crashing when Alyx loads a new area in the quarantine zone, was opened on November 9, 2020 and has 24 comments. Issue #784 was opened on May 8, 2025 and issue #801 on August 15, 2025.
What the reports establish, and what they do not
Valve has said nothing publicly about the barnacle crash. Its only reply anywhere near these reports concerns the train-ride assert, so nothing on the tracker amounts to an acknowledgement that the spray crash exists, let alone a fix for it.
Nor do the reports pin it on the Steam Frame, although all three reporters use one. Two GPU vendors and two driver stacks are involved, and the stack traces carry no GPU driver frames. The factor the three reports share is the native Linux binary rather than the headset: the second reporter played two sessions under Proton without a crash, while saying a barnacle kill had not been retested there.
There is also no scale here. Each account gives its own crash count and nobody has published a figure for how many owners hit this, which is the usual limit of a public bug tracker. Two of the accounts separately mention audio crackling in the native build that the Proton build does not have, and only in this game.
Reproducing it does not take much, by the first report's account: start SteamVR, launch the native build, shoot a barnacle while looking at it, and the game exits. That reporter says the crash also happens with the Steam client beta, the SteamVR beta and SteamOS Preview, the same beta track Valve has been pointing Steam Frame owners at to clear its Error 17 streaming fault.
No fix is attached to anything on the tracker. Issue #983 has been open since October 3 with no Valve comment on it, and #405, the oldest of the three issues the duplicate closure pointed at, has been open for just under six years.