Having the exact same issues, anytime I go into pass through on the Quest 3s SteamVR crashes
Is this still happening for you under the latest SteamVR? I can't reproduce it with current SteamVR and Steam Link app (and Space Pirate Trainer as the test game that's running).
Is this still happening for you under the latest SteamVR? I can't reproduce it with current SteamVR and Steam Link app (and Space Pirate Trainer as the test game that's running).
https://github.com/ValveSoftware/SteamVR-for-Linux/issues/842#issuecomment-4138375001
Still reproducible on SteamVR 2.17.2 beta as of 2026-06-12. Since this issue is on Need Retest — here is fresh evidence.
Setup
qvlclient;eureka;2.0.22.2080Deterministic repro
Very brief crossings (<~5 s pause) usually recover; longer pauses never do.
Host log signature (driver_vrlink.txt): after re-entry the client keeps escalating stream reset requests, the host recreates the Vulkan video session each time (Created vkCreateVideoSessionParametersKHR! after every reset), but no video packet is ever accepted again — the driver strikes out after 7 retries:
23:12:38.638436 - Reset video stream because we had a stream reset request [wgpReset:7 != lastReset:6]
23:12:38.731890 - Reset video stream because we had a stream reset request [wgpReset:8 != lastReset:7]
23:12:38.944711 - Reset video stream because we had a stream reset request [wgpReset:9 != lastReset:8]
23:12:39.243608 - Timed out waiting for another accepted video packet, trying to force the stream reset
23:12:39.243714 - HandleUnrecoverableError( 1 )
...
23:15:08.640233 - Timed out waiting for another accepted video packet, trying to force the stream reset
23:15:08.640331 - HandleUnrecoverableError( 6 )
23:15:09.050426 - Timed out waiting for another accepted video packet, trying to force the stream reset
23:15:09.050494 - HandleUnrecoverableError( 7 )
23:15:09.932590 - Connection inactive at 232.309237
On the resume attempt vrserver.txt also logs:
[Error] - VendorSpecificEvent 110 for tracked device index not owned by driver
vrlink: New Session detected; Invalidating.
Mitigations tried that do NOT help
power.turnOffScreensTimeout: 1800 + power.pauseCompositorOnStandby: false in steamvr.vrsettings (removes the host standby path entirely — failure signature unchanged)The #876 teardown fix in the 2.17.x beta works for me (restarts are clean now), but this resume bug is distinct and still present. Happy to provide full logs or run a debug build if useful.
@Packetdancer Sorry, I never saw the notification. Yes, this is still happening to me as well with the latest SteamVR beta.
Nothing extracted yet.
Describe the bug
On a Quest 3, the stream only seems to work when it's not interrupted. If I double tap the side of the headset to enter passthrough mode, or press the power button to put it to sleep or anything of the sort, the Steam VR Link stream will crash and I won't be able to go back into the game. The game will also close and even the Steam client seems to restart itself.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should not crash and I should be able to resume the stream
System Information (please complete the following information):
steamruntimeinfo.txt
steam-logs.tar.gz
steam-minidumps.tar.gz
Screenshots
Additional context
Using a 4070Ti Super for streaming. On KDE Plasma, with a Wayland session. Nvidia driver 580.105.08