[BUG | 2.17.3] Steam Link drops connection with 450 error and Steam + SteamVR hangs

[sera-ina]

I have this bug often where I randomly get the 450 error where I can still hear the sound a bit on the HMD as well as still see a bit of stuttery headset movement on the game on the monitor before Steam entirely hangs. Steam, SteamVr, Game become unresponsive and I have to kill the steam process with pfkill.

steam-logs.tar.gz

To Reproduce
Steps to reproduce the behavior:

Happens randomly. On starting the link, on starting the game, or before anything of that. But most consistently I could do that in the game "Into the Radius 2" when traversing between areas. In general it will cause that issue with a 50/50 chance.

System Information (please complete the following information):
Steam Version: 2.17.3
OS: Arch Linux
Kernel: 7.1
CPU: Ryzen 5 5600
GPU: RTX 5060 Ti 16GB - 610.43.02
RAM: 32GB DDR4

[Packetdancer]

Could you snag vrcompositor.txt and driver_vrlink.txt from ~/.steam/steam/logs/ and throw them somewhere that I can snag them to look at?

[sera-ina]

Aren't the one in the provided zip file enough? Else, here are the same files that are in there.

vrcompositor.txt

driver_vrlink.txt

[slice-the-idiot]

i'm having a very similar issue

[sera-ina]

logcat_quest3.log

Adding the logcat output from "com.valvesoftware" from right now.

Game tested with was "Into the Radius 2". I was able to load into the game (past menu) but just 2 seconds in I got booted again with the 450 error.

[Packetdancer]

@sera-ina -- Hm. Getting booted after the game started is interesting. Normally I expect to see a 450 on connect; getting it partway through means for some reason you got disconnected from the host and it couldn't reconnect. Do you happen to have the driver_vrlink.txt for the same session as the logcat? If so, I have a theory (and if the timestamps for something match up in the VRLink host-side log, this may have finally given the necessary clue to figure this particular issue out once and for all).

Also sorry I missed the tarball of logs originally -- it wasn't in the normal format, so the little Python tool I wrote that slurps in new tickets to my local tracking sheet flagged this as missing logs and I didn't double-check. I should make it just look for any links that have a tarball in the originating post, rather than for the specific templated format. :)

[sera-ina]

@Packetdancer

Sure. When it happened just now, StemVR also "failed" with error code "-301". So I added vrmonitor and vrcompositor too

steam_logcat.log
driver_vrlink.txt

vrmonitor.txt
vrcompositor.txt

Also made a video to show it (was made with the last session from the reports now). The crash happens at 2:58. You can see that I could play it for a while, then it just crashed with 450
https://www.youtube.com/watch?v=pQDFvVg4LQE