[BUG] SteamVR error 303
Same with my setup:
Operating System: Arch Linux
KDE Plasma Version: 6.6.3
KDE Frameworks Version: 6.24.0
Qt Version: 6.11.0
Kernel Version: 6.19.10-zen1-1-zen (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz
Memory: 26 GB of RAM (25,1 GB usable)
Graphics Processor: AMD Radeon RX 6750 XT
SteamVR version: 2.16.1
I have just discovered that killing my X compositor (picom) and trying to launch SteamVR completely segfaults my nvidia drivers and kills my complete X session.
My friend got her screen barrel projected by doing this. What is going on?
[2026-04-08 03:46:45] Backtrace:
[2026-04-08 03:46:45] 0: /usr/bin/X (xorg_backtrace+0x54) [0x560228889864]
[2026-04-08 03:46:45] 1: /usr/bin/X (0x560228747000+0x14b33f) [0x56022889233f]
[2026-04-08 03:46:45] 2: /usr/lib64/libc.so.6 (0x7f115117f000+0x419e0) [0x7f11511c09e0]
[2026-04-08 03:46:45] 3: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f1150800000+0xa0d78) [0x7f11508a0d78]
[2026-04-08 03:46:45] 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f1150800000+0x8aa2e) [0x7f115088aa2e]
[2026-04-08 03:46:45] 5: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f1150800000+0x26d0e6) [0x7f1150a6d0e6]
[2026-04-08 03:46:45]
[2026-04-08 03:46:45] Segmentation fault at address 0x508
[2026-04-08 03:46:45]
Fatal server error:
[2026-04-08 03:46:45] Caught signal 11 (Segmentation fault). Server aborting
[2026-04-08 03:46:45]
[2026-04-08 03:46:45]
Please consult the XLibre support: https://www.xlibre.net/
[2026-04-08 03:46:45] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[2026-04-08 03:46:45]
[2026-04-08 03:46:45] (EE) Server terminated with error (1). Closing log file.
I'm getting this too, though I also have logs similar to #880
vrcompositorASSERT: "Unhandled sampler filter type!" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:2288.
vrcompositorWed Apr 08 2026 17:01:39.535824 [Error] - ASSERT: "IsDepthFormat(eVkFormat)" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:762.
I notice that after SteamVR starts up, if I go to the settings, the resolution and refresh rate are not what I expect - if I set to 72Hz it sticks at 90 and no matter what resolution I pick, it shows 800x900 as the render resolution. I'm using ALVR on Bazzite. AMD 7900XTX, Quest 3 (though this issue occurs before the headset even connects). I tried disabling direct mode but it restarted with it still enabled which is not unexpected.
Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/879#issuecomment-4209675807
I get the same error when I run steam with these environment options in my terminal on Xlibre (X11): dbus-launch --exit-with-session steam
Thu Apr 09 2026 02:57:47.479269 [Error] - ASSERT: "IsDepthFormat(eVkFormat)" at /data/src/common/vrcommon/vrrenderer/vulkanrenderer.cpp:762.
Full log: steam-logs-with-envs-AND-dbus.tar.gz
Note: I do not run dbus globally and avoid it which is why dbus-launch was necessary, there seems to be some sort of issue with steam trying to execute a broken dbus-launch as seen here:
<3>steam-runtime-launch-client[45206]: E: Can't find session bus: Failed to execute child process ?dbus-launch? (No such file or directory)
I will create a seperate issue for this probably.
Here is a log with the same ENV vars as above but without dbus: steam-logs-with-vars-without-dbus.tar.gz
Still relevant for SteamVR Beta 2.16.3
Yah confirmed still broken in Beta 2.16.3 as well. SteamVR has been bust for me on Linux in every version 2.16.x. Reverting to 2.15.x (previous branch in Steam) is the workaround.
Replying to [#879 (Comment)](https://github.com/ValveSoftware/SteamVR-for-Linux/issues/879#issuecomment-4240010453)
Are you sure you're not suffering from #880?
The main issue this report addresses is present on all SteamVR versions and can only be fixed using following workaround:
$ dbus-launch --exit-with-session steam
And I assume it has something to do with this log output:
<3>steam-runtime-launch-client[45206]: E: Can't find session bus: Failed to execute child process ?dbus-launch? (No such file or directory)
Can you test whether it works for you if you set the refresh rate below 144hz? It somehow fixed my error 303
To double-check: everyone having this issue is on a wired headset, yes?
Can you test whether it works for you if you set the refresh rate below 144hz? It somehow fixed my error 303
On a brand new steamvr config, it does the same unless steam is launched with dbus-launch for me.
To double-check: everyone having this issue is on a wired headset, yes?
Yep, Valve Index in my case.
On my end it only occurs on Beta using Steam Native, using Steam Linux Runtime or switching to SteamVR Stable works, though this is not preferred for performance reasons. (Valve Index, so no ALVR)
Getting the same issue with the beta branch, though my setup is a 3060ti and a Quest 2 running through ALVR (USB). Reverting back to the default stable branch fixes this.
Does it crash without ALVR in the mix? (If you try using Steam Link just to test, for instance.)
@Packetdancer Thankfully, no - no error with the beta when the edited CLI command is removed, but then obviously no headset is detected.
I'm going to assume the ALVR issue is probably not directly the same thing, then. Last I checked ALVR tries to move vrcompositor out of the way and replace it with its own proxy layer, so I suspect the ALVR crashes may be happening as a result of that.
For everyone else seeing issues with the wired headsets... just out of curiosity, do you see the same problems if you run SteamVR outside of the Steam pressure vessel? Go to ~/.steam/steam/steamapps/common/SteamVR or wherever you have the SteamVR beta installed, then:
cd bin/linux64
../vrenv.sh ./vrmonitor
...I have a nagging suspicion this won't work, but will fail in a different and potentially-informative manner.
...I have a nagging suspicion this won't work, but will fail in a different and potentially-informative manner.
https://paste.sh/ru0LaKyD#K1NmeNcDSZo4chWXi5sIV1ee
Results in a -203 error now for me, possibly related to something else
We could be dealing with multiple bugs in this report, because it works on my machine.
When launching from Steam, I get the same 303 error. But by launching SteamVR outside the pressure vessel, it seems to be working as usual.
Feel free to ask clarifying questions
System Information:
- Steam client version (build number or date): Steam Beta Update 1780098236
- SteamVR version: 2.16.5]
- Headset: Valve Index
- Distribution (e.g. Ubuntu): Arch Linux
- Kernel Version: Linux 7.0.9-zen1-1-zen
- Steam runtime diagnostics: stean_runtime_diagnostics.txt
- Steam and SteamVR logs: steam-logs.tar.gz
- Minidumps: steam-minidumps.tar.gz
@authorisation - I would be very interested in a vrcompositor.txt for a -203 run. -203 generally means vrcompositor crashed.
If you want to get really fancy, you can go to the same bin/linux64 directory as before and
../vrenv.sh ./vrserver -keepalive
...in one terminal and then...
../vrenv.sh ./vrcompositor
...in another to see what vrcompositor actually spews to console (if anything).
(I don't recommend running that way usually because you'll be missing the vrmonitor window, but it is sometimes useful.)
If you want to get really fancy, you can go to the same bin/linux64 directory as before and
../vrenv.sh ./vrserver -keepalive...in one terminal and then...
../vrenv.sh ./vrcompositor
Here's both terminal output, just leads to a crash with minidumps being generated again, vrserver just does nothing after initializing. No window or anything opens up even.
https://paste.sh/eHL0NGFe#xx_TZwUH6MTpXgiWI-iUcHHY
The window comes from vrmonitor—it's why I said I don't recommend running this was unless you really have a reason (namely, testing something), since you'll have no UI. :)
That said, thank you; the dump ID will be useful. I'll take a look when back in the office.
Still broken in 2.16.6 (v1780421623), now also confirmed on NVIDIA.
Arch Linux (kernel 7.0.10), KDE Plasma 6.6.5, RTX 5080 (driver 595.71.05), ALVR 20.14.1 + Quest 3S. Reproduced on both Wayland and X11 (WAYLAND_DISPLAY='').
Every 2.16.6 launch, vrmonitor.txt:
VR_Init successful
Unable to get compositor interface (303)
while vrcompositor.txt shows the compositor fully initialized ("Startup Complete", ALVR direct-mode display acquired) — vrserver/vrmonitor just never attach to its pipe. 2.16.6 also logs Failed to set thread priority: setschedparam failed 15: 1 on every run, which 2.15.6 did not. Also seeing repeated vrwebhelper SIGSEGV/SIGTRAP coredumps like in #733.
2.15.6 worked fine until the update; switching to the previous branch (2.12.14) fixes it immediately on the same session, no other changes.
2.17.1 still throws the 303 error unless run with ../vrenv.sh ./vrmonitor, in which case it runs fine
Hey any updates on this? I've also been having it since around 2.16.2 (i do not remember exactly).
Launching it via
cd ~/.steam/steam/steamapps/common/SteamVR/bin/linux64
../vrenv.sh ./vrmonitor
works but its kinda annoying.
I can provide my logs and system configuration if it would help getting this resolved, but i'm mostly just curios if anything is still happening with this since the issue hasn't had any recent comments?
The problem is that 303 is "compositor init failed" which could be for a variety of reasons.
If folks are still having this (specifically 303, not some other error) with 2.17, I would be interested in their vrcompositor.txt
That said, there's just been work done to make how SteamVR launches a bit more sane, and I suspect that will fix it for everyone where it works when run via the command line but not from in Steam.
I would be interested in their vrcompositor.txt
weirdly that file does not get updated in my case if i launch steam vr from steam.
I've attached all the vr-prefixed files that change in a zip if its of use.
Also KDE Plasma specifically says that "vrmonitor" is the thing that crashes after a while of 303 appearing
Same issue here #303 and vrcompositor segfaults on startup. System is NixOS 26.05 (kernel 7.1.3) with Nvidia driver 580.173.02 and SteamVR 2.16.7. Beta 2.17.6 shows the same behavior. Same setup worked perfectly last year.
For anyone following this, it appears to be resolved (for me at least) in beta 2.17.7
Update: deleting my ~/.steam folder and starting with Steam from scratch did indeed fix the problem, I can now boot up VR without the error. Original post left below for those with the same problem:
I'm also having error 303 with an Index headset, running on Kubuntu 26.04, SteamVR beta 2.17.7. Launching via the mentioned `../vrenv.sh ./vrmonitor` command boots up the vrmonitor process as normal, but after twenty seconds or so, I get a message box saying "SteamVR has encountered a critical error" (this doesn't show up with just running it through Steam, but the error still happens there).
vrmonitor terminal log
matt@kubuntu-desktop:~/.steam/steam/steamapps/common/SteamVR/bin/linux64$ ../vrenv.sh ./vrmonitor >> vrmonitor_log.txt vrenv.sh[16822]: VRCOMPOSITOR_LD_LIBRARY_PATH=/home/matt/.steam/steam/steamapps/common/SteamVR/bin/linux64:/home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64 vrenv.sh[16822]: exec ./vrmonitor Using breakpad crash handler Setting breakpad minidump AppID = 250820 Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit 08/17 12:23:19 minidumps folder is set to /tmp/dumps 08/17 12:23:19 Init: Installing breakpad exception handler for appid(250820)/version(2.17.7)/tid(16822) sh: 1: steamxdg-icon-resource: not found libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile CQVRMonitorHeadsetWarning(0x5c01084b9650) does not have a property named "green_color" CQVRMonitorHeadsetWarning(0x5c01084b9650) does not have a property named "red_color" Using breakpad crash handler Setting breakpad minidump AppID = 250820 Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit 08/17 12:23:20 minidumps folder is set to /tmp/dumps 08/17 12:23:20 Init: Installing breakpad exception handler for appid(250820)/version(2.17.7)/tid(16926) [S_API] SteamAPI_Init(): Loaded '/home/matt/.steam/debian-installation/linux64/steamclient.so' OK. Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197996292128 [API loaded yes] SteamInternal_SetMinidumpSteamID: Setting Steam ID: 76561197996292128 vrcompositor-launcher.sh[16958]: Relaunch under scout LDLP runtime. vrcompositor-launcher.sh[16958]: exec /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh: line 37: /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh: No such file or directory Using breakpad crash handler Setting breakpad minidump AppID = 250820 Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit 08/17 12:23:27 minidumps folder is set to /tmp/dumps 08/17 12:23:27 Init: Installing breakpad exception handler for appid(250820)/version(2.17.7)/tid(16970) libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile [S_API] SteamAPI_Init(): Loaded '/home/matt/.steam/debian-installation/linux64/steamclient.so' OK. Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit SteamInternal_SetMinidumpSteamID: Caching Steam ID: 76561197996292128 [API loaded yes] SteamInternal_SetMinidumpSteamID: Setting Steam ID: 76561197996292128 Initialize() is failed!!! qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings qt.network.ssl: QSslSocket: cannot resolve sk_new_null qt.network.ssl: QSslSocket: cannot resolve sk_push qt.network.ssl: QSslSocket: cannot resolve sk_free qt.network.ssl: QSslSocket: cannot resolve sk_num qt.network.ssl: QSslSocket: cannot resolve sk_pop_free qt.network.ssl: QSslSocket: cannot resolve sk_value qt.network.ssl: QSslSocket: cannot resolve SSL_get_peer_certificate qt.network.ssl: QSslSocket: cannot resolve SSL_library_init qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index qt.network.ssl: QSslSocket: cannot resolve SSLv2_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method qt.network.ssl: QSslSocket: cannot resolve SSLv2_server_method qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf qt.network.ssl: QSslSocket: cannot resolve SSLeay qt.network.ssl: QSslSocket: cannot resolve SSLeay_version qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback qt.network.ssl: QSslSocket: cannot call unresolved function SSL_library_init qt.network.ssl: QSslSocket: cannot call unresolved function SSLv23_client_method qt.network.ssl: QSslSocket: cannot call unresolved function sk_num vrcompositor-launcher.sh[16982]: Relaunch under scout LDLP runtime. vrcompositor-launcher.sh[16982]: exec /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh: line 37: /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh: No such file or directory QSplitter::setCollapsible: Index 1 out of range libpng warning: iCCP: known incorrect sRGB profile libpng warning: iCCP: known incorrect sRGB profile Using breakpad crash handler Using breakpad crash handler Setting breakpad minidump AppID = 250820 Forcing breakpad minidump interfaces to load Setting breakpad minidump AppID = 250820 Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit 08/17 12:23:34 minidumps folder is set to /tmp/dumps 08/17 12:23:34 Init: Installing breakpad exception handler for appid(250820)/version(2.17.7)/tid(17009) 08/17 12:23:34 minidumps folder is set to /tmp/dumps 08/17 12:23:34 Init: Installing breakpad exception handler for appid(250820)/version(2.17.7)/tid(17008) WARNING: radv is not a conformant Vulkan implementation, testing use only. Using breakpad crash handler Setting breakpad minidump AppID = 250820 Forcing breakpad minidump interfaces to load Looking up breakpad interfaces from steamclient Calling BreakpadMiniDumpSystemInit 08/17 12:23:42 minidumps folder is set to /tmp/dumps 08/17 12:23:42 Init: Installing breakpad exception handler for appid(250820)/version(2.17.7)/tid(17071) WARNING: radv is not a conformant Vulkan implementation, testing use only. vrcompositor-launcher.sh[17167]: Relaunch under scout LDLP runtime. vrcompositor-launcher.sh[17167]: exec /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh: line 37: /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh: No such file or directory vrcompositor-launcher.sh[17190]: Relaunch under scout LDLP runtime. vrcompositor-launcher.sh[17190]: exec /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh /home/matt/.steam/debian-installation/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh: line 37: /home/matt/.steam/root/ubuntu12_32/steam-runtime/run.sh: No such file or directory assert_20260817122402_4.dmp[17211]: Uploading dump (out-of-process) /tmp/dumps/assert_20260817122402_4.dmp assert_20260817122402_4.dmp[17211]: Finished uploading minidump (out-of-process): success = no assert_20260817122402_4.dmp[17211]: error: libcurl.so: cannot open shared object file: No such file or directory assert_20260817122402_4.dmp[17211]: file ''/tmp/dumps/assert_20260817122402_4.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory'' crash_20260817122402_5.dmp[17214]: Uploading dump (out-of-process) /tmp/dumps/crash_20260817122402_5.dmp crash_20260817122402_5.dmp[17214]: Finished uploading minidump (out-of-process): success = no crash_20260817122402_5.dmp[17214]: error: libcurl.so: cannot open shared object file: No such file or directory crash_20260817122402_5.dmp[17214]: file ''/tmp/dumps/crash_20260817122402_5.dmp'', upload no: ''libcurl.so: cannot open shared object file: No such file or directory'' [0817/122403.059966:ERROR:check.cc(376)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry! Destroy() is failed!! qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_num_locks qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_id_callback qt.network.ssl: QSslSocket: cannot call unresolved function CRYPTO_set_locking_callback qt.network.ssl: QSslSocket: cannot call unresolved function ERR_free_strings
It seems to be looking for ~/.steam/root/ubuntu12_32/steam_runtime/run.sh, which is a broken symlink to ../legacy-run-stub.sh which doesn't exist in the folder for me.
I've re-installed SteamVR, tried the current stable version (2.16) and the previous branch (I believe 2.12), all of them give me this error. This home partition has persisted across multiple versions of Ubuntu/Kubuntu, though I've had to re-install Steam itself via the deb package from the website with each one - does all of Steam need wiping and re-installing?
Does somebody know what the specific fix for this would be rather than deleting .steam?
Update: deleting my
~/.steamfolder and starting with Steam from scratch did indeed fix the problem, I can now boot up VR without the error. Original post left below for those with the same problem:
I had the same issue and deleting ~/.local/share/Steam/bootstrap.tar.xz, ~/.local/share/Steam/ubuntu12_32 and ~/.local/share/Steam/ubuntu12_64 resolved it. Just deleting ~/.steam didn't work in my situation. Thanks for pointing me in the right direction.
Sharing my experiences with this error.
In my case, deleting ~/.local/share/Steam/bootstrap.tar.xz, ~/.local/share/Steam/ubuntu12_32 and ~/.local/share/Steam/ubuntu12_64 did not help, nor did starting Steam with dbus-launch --exit-with-session steam
Turns out, I had enabled SteamRT3 in Steam --> Settings --> Interface --> Use experimental SteamRT3 Steam Client.
Once I disabled that and restarted Steam, SteamVR started working.
Why did it not work with SteamRT3, when it definitely worked before? I don't know, but hope this helps a little bit.
The only way I could get SteamVR to run in SteamRT3, was to change the location of run.sh in
~/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh to point to a different directory.
This is obviously not the way to launch SteamVR.
Reporting in with same error - the timing tho alarmed me quite a lot!
I've been in the middle of Elite Dangerous, and out of nowhere - my HMD display and my monitors just went black. Keyboard was unresponsive too - I assumed a power blackout but turns out machine was still on so I rebooted, and everything seemed to work fine - except that SteamVR (any version I tried, stable, beta, previous) would give off 303, the vrcompositor-la would sit stuck.
Also running Arch.
However @wallcarpet40 gave me a pattern:
Turns out, I had enabled SteamRT3 in Steam --> Settings --> Interface --> Use experimental SteamRT3 Steam Client.
I was using Steam Beta, and reverting to normal Steam - everything started working, as well.
Would never think the issue was there, I started thinking faulty display ports and/or cables.
I can confirm that disabling experimental SteamRT3 Steam Client fixed it for me also.
Nothing extracted yet.
Describe the bug
SteamVR upon launching, hangs for 10 seconds in a black (or seethrough with a compositor enabled) window and then emits a 303 critical error.
Terminal output, when steam is run from the terminal, indicates some sort of crash and a crash dump gets generated.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
SteamVR launches successfully, vrcompositor runs and no errors get reported.
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
Screenshots
Additional context
I am running a custom configured Linux kernel on version 6.18.18.
Running vrcompositor with its launcher shell script does absolutely nothing and it results in a crash, maybe intended? Maybe not. vrcompositor-launch-log.txt
Running the binary does the same but I assume it is not intended to be ran like that anyways.
Months ago on the same exact system and install it worked absolutely fine.