Closed freedg closed 6 months ago
Watched journalctl while launching VR: SteamVR processes are coredumping, and the vrcompositor trace is pointing at amdvlk64.so
Hello @freedg, can you test how SteamVR behaves with mesa/RADV instead of AMDVLK?
Hello @freedg, can you test how SteamVR behaves with mesa/RADV instead of AMDVLK?
I was actually just doing that, I thought I was using mesa. I uninstalled amdvlk and lib32-amdvlk and rebooted. Still getting 109, and now I'm getting Failed to connect to headset display (496) instead of the 307 error. Steam's System Information is now correctly reporting that I have my Index connected as well. vulkaninfo | grep driverInfo
is showing Mesa 23.1.9-manjaro1.1.
Here is a new SteamVR system report. https://gist.github.com/freedg/fe543a832a1ae1d65b1956c62ebcbb72
I am also now getting the same 109/496 error in Flatpak SteamVR 2.2.3. Beta 2.2.4 does not launch.
Was futzing with it a bit, manually set refresh rate to 90 in steamvr.vrsettings, did a file verify and added gamemoderun to SteamVR's launch parameters, and now VR is launching and the headset is working. Removed gamemoderun, and it is still working. But I am stuck in the default environment. I can open the Steam VR overlay, but I cannot launch any games. https://gist.github.com/freedg/98198a1ccbf39102904f40a50d4cb1b1
edit: also vrwebhelper is segfaulting 3 or 4 times per launch still, in libcef.so
I suppose for the sake of completeness, here is a system report of SteamVR 2.2.4 working without any issues on my Windows dual-boot. Windows-SteamVR-2023-12-29-AM_07_52_20.txt
did a file verify and added gamemoderun to SteamVR's launch parameters
Using an original HTC Vive, I was getting the same until I did this as well. The verify process did replace one file (is which one reported anywhere?). I also do not get the Home environment, but I can launch games from the overlay menu now.
Hopefully this isn't just irrelevant info/noise, but: I have used ALVR on this system as well, and I did also start that up at one point to unregister its driver. I had also had issues with the steam options not displaying, but just moved the steamvr.vrsettings file and that's working again as well.
I'll try to return with some better info (and system report) if I get this again/when I have more time to bang on it and try making it work better than it presently is.
@freedg can i have your steamvr.vrsettings file? i dont see where to put the refresh rate part on mine
I would also like that steamvr.vrsettings file, if possible.
@BrassDude i got it fixed, didn't need to change the vrsettings file at all, just a reboot worked for me.
Getting a different error now. Headset now boots and loads into the default VR environment with tracking, but I'm getting the error "Could not start SteamVR Room Setup: Another application was already starting." and "Please perform Room Setup to begin using SteamVR. (C201)" This appears even right after a reboot. It looks like the center of the floor is set to one of my lighthouses. Clicking the room setup button just re-appears the "Could not start SteamVR Room Setup" error.
SteamVR-2024-01-07-PM_10_20_40.txt
@makerio90 / @BrassDude I had deleted and verified by steamvr.vrsettings, so I don't think there would be anything interesting in my config. That said, "preferredRefreshRate" : 90
(or 120/144) would go in the "steamvr" category in config/steamvr.vrsettings.
I have the same issue with htc vive, an ASUS B550-A mainboard, a Ryzen 7 5700G, Radeon RX 7900 XT, running up to date arch linux.
The very same system and OS but with an RX5700XT GPU works without any issue. Maybe this has something to do with RDNA 3?? Attached SteamVR-2024-01-30-PM_07_14_56.txt system report.
I also tried my GPD win max 2 (also running arch, also RDNA 3 graphics) and got the same Error 109.
Has anyone been able to get SteamVR working? I'm also having this same issue, error 109 cannot initialize.
I can get SteamVR to launch and see all of my devices: headset; stations; controllers, but vrwebhelper continuously segfaults and complains about Qt5 not being entirely loaded despite ldd
showing all 30+ dependencies are found on the executable that's segfaulting.
Specs: Fedora 39 x86_64 Workstation Edition, Gnome X11, HTC Vive Pro w/ Eye-Tracking, SteamVR Beta 2.4.1, Asus X99-Deluxe mainboard, NVIDIA GeForce RTX 3090 FTW3 ULTRA w/ proprietary drivers loaded & secureboot enabled.
I see in the udev rules that Steam/SteamVR is permitted to access USB devices, though I'm unsure if my devices are listed in the configuration. I still need to cross-check vendor ids from dmesg/lsusb.
This screenshot below is as far as I can get it to work. I can start up my VR games and see an environment from my PC Monitors, but SteamVR is completely broken and unusable, and the headset doesn't even turn on its eye displays despite showing connected.
I'll upload a SteamVR report log file later, I took a break after trying to even get it this far. This is better than SteamVR just not even launching. Pretty frustrating, since this same configuration works 100% on Windows 10.
I experience this as well. Error 109 in the Steam client and error 496 inside SteamVR. None of the suggested fixes has worked for me.
GPU: Nvidia GTX 1080Ti CPU: AMD Ryzen 7 5700G (iGPU is disabled through BIOS) Drivers, Kernel, Steam and SteamVR are all updated to the latest version.
Hadn't tried again since Jan 7th; now getting errors 109 and 496. SteamVR-2024-02-26-PM_06_04_47.txt All of my logs so far have been in X11, but this time I also tried in Wayland. Still no luck though, same errors.
I got the same error on Kubuntu 23.10 and it was due to cables being poorly connected. Reconnecting (and restarting Steam or SteamVR?) fixed it on two occasions. 😅
im on ultramarine (fedora) and im getting this error with wayland and kde plasma
I also get the same error, on KDE Plasma 6 (X11 session), with my HTC Vive. I tried both 2.3.5 and beta 2.4.2 of SteamVR.
System report: SteamVR-2024-03-11-PM_07_30_48.txt
Same error on Artix ,I have a rx6800xt
I just suffered with this error for a while. Turns out that the display port cable had become unplugged from the graphics card, and this seems to be the error you get when in this condition.
(Edit: this is not to say there aren't other conditions that can cause this error, but hopefully this might help others).
I've just tried now again since my last report in February, and it is working now! Steam beta 2.5.1. I did have to verify integrity and downgrade to stable 2.4.4.
Initially today I was getting the C201, Room setup/App already running whenever trying to launch SteamVR in 2.5.1, but I verified my files and switched to the stable branch, which seemed to clear my config. Once on stable, the room setup app launched successfully, and after doing the setup, I was able to run all my SteamVR stuff without any errors.
I also have switched back to the beta branch, and still no errors. Now able to launch and play games in 2.5.1 and 2.4.4.
I've just tried now again since my last report in February, and it is working now! Steam beta 2.5.1. I did have to verify integrity and downgrade to stable 2.4.4.
Initially today I was getting the C201, Room setup/App already running whenever trying to launch SteamVR in 2.5.1, but I verified my files and switched to the stable branch, which seemed to clear my config. Once on stable, the room setup app launched successfully, and after doing the setup, I was able to run all my SteamVR stuff without any errors.
I also have switched back to the beta branch, and still no errors. Now able to launch and play games in 2.5.1 and 2.4.4.
Are you on X11 or Wayland?
Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/667#issuecomment-2044124586
This was all in Wayland. Switching to X11, SteamVR beta 2.5.1 opens and works, but I can't open certain games. I click play and it thinks for maybe 3-5 seconds before the button just goes back to play, and the game never opens. This behavior is happening with Jet Island and Hot Dogs, Horseshoes & Hand Grenades, but not with Escape Simulator VR Demo. I was able to play H3VR yesterday. This persisted when I switched back to Wayland too. Not sure if something changed between today and yesterday, or if switching to X11 caused this. X11 report: SteamVR-2024-04-09-PM_05_37_18.txt
Switching back to stable 2.4.4: SteamVR and launching and playing all games is working in Wayland and X11.
Is there any known way to fix this ? SteamVR used to work for a while in my case and now it always crashes. Doesnt matter if I am on wayland or X11, KDE or Hyprland...
Apr 16 11:36:22 crashtux systemd-coredump[61915]: [🡕] Process 61894 (vrwebhelper) of user 1000 dumped core.
Module libVkLayer_obs_vkcapture.so from rpm obs-studio-plugin-vkcapture-1.5.0-1.fc39.x86_64
Module libwayland-client.so.0 from rpm wayland-1.22.0-2.fc39.x86_64
Module libVkLayer_MESA_device_select.so from rpm mesa-vulkan-drivers-24.1.0-git.20240412.e511ffe.fc39.x86_64
Module libvulkan.so.1 from rpm vulkan-loader-1.3.280-1.fc39.x86_64
Module libxcb-sync.so.1 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libxcb-present.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libxcb-randr.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libxcb-glx.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libGLdispatch.so.0 from rpm libglvnd-1.7.0-1.fc39.x86_64
Module libGLX.so.0 from rpm libglvnd-1.7.0-1.fc39.x86_64
Module libGL.so.1 from rpm libglvnd-1.7.0-1.fc39.x86_64
Module libbrotlicommon.so.1 from rpm brotli-1.1.0-1.fc39.x86_64
Module libbrotlidec.so.1 from rpm brotli-1.1.0-1.fc39.x86_64
Module libbz2.so.1 from rpm bzip2-1.0.8-16.fc39.x86_64
Module libgmp.so.10 from rpm gmp-6.2.1-5.fc39.x86_64
Module libhogweed.so.6 from rpm nettle-3.9.1-2.fc39.x86_64
Module libnettle.so.8 from rpm nettle-3.9.1-2.fc39.x86_64
Module libtasn1.so.6 from rpm libtasn1-4.19.0-3.fc39.x86_64
Module libunistring.so.5 from rpm libunistring-1.1-5.fc39.x86_64
Module libidn2.so.0 from rpm libidn2-2.3.7-1.fc39.x86_64
Module libp11-kit.so.0 from rpm p11-kit-0.25.3-1.fc39.x86_64
Module libcrypto.so.3 from rpm openssl-3.1.1-4.fc39.x86_64
Module libkeyutils.so.1 from rpm keyutils-1.6.3-1.fc39.x86_64
Module libkrb5support.so.0 from rpm krb5-1.21.2-3.fc39.x86_64
Module libcom_err.so.2 from rpm e2fsprogs-1.47.0-2.fc39.x86_64
Module libk5crypto.so.3 from rpm krb5-1.21.2-3.fc39.x86_64
Module libkrb5.so.3 from rpm krb5-1.21.2-3.fc39.x86_64
Module libdatrie.so.1 from rpm libdatrie-0.2.13-7.fc39.x86_64
Module libpixman-1.so.0 from rpm pixman-0.42.2-2.fc39.x86_64
Module libxcb-shm.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libxcb-render.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libpng16.so.16 from rpm libpng-1.6.37-15.fc39.x86_64
Module libxml2.so.2 from rpm libxml2-2.10.4-3.fc39.x86_64
Module libgraphite2.so.3 from rpm graphite2-1.3.14-12.fc39.x86_64
Module libfreetype.so.6 from rpm freetype-2.13.1-2.fc39.x86_64
Module libzstd.so.1 from rpm zstd-1.5.6-1.fc39.x86_64
Module liblzma.so.5 from rpm xz-5.4.4-1.fc39.x86_64
Module liblz4.so.1 from rpm lz4-1.9.4-4.fc39.x86_64
Module libcap.so.2 from rpm libcap-2.48-9.fc39.x86_64
Module libblkid.so.1 from rpm util-linux-2.39.3-6.fc39.x86_64
Module libgnutls.so.30 from rpm gnutls-3.8.4-1.fc39.x86_64
Module libavahi-client.so.3 from rpm avahi-0.8-24.fc39.x86_64
Module libavahi-common.so.3 from rpm avahi-0.8-24.fc39.x86_64
Module libgssapi_krb5.so.2 from rpm krb5-1.21.2-3.fc39.x86_64
Module libthai.so.0 from rpm libthai-0.1.29-6.fc39.x86_64
Module libfribidi.so.0 from rpm fribidi-1.0.13-2.fc39.x86_64
Module libcairo.so.2 from rpm cairo-1.18.0-1.fc39.x86_64
Module libfontconfig.so.1 from rpm fontconfig-2.14.2-6.fc39.x86_64
Module libharfbuzz.so.0 from rpm harfbuzz-8.2.1-2.fc39.x86_64
Module libpangoft2-1.0.so.0 from rpm pango-1.51.0-1.fc39.x86_64
Module libsystemd.so.0 from rpm systemd-254.10-1.fc39.x86_64
Module libselinux.so.1 from rpm libselinux-3.5-5.fc39.x86_64
Module libmount.so.1 from rpm util-linux-2.39.3-6.fc39.x86_64
Module libz.so.1 from rpm zlib-1.2.13-4.fc39.x86_64
Module libgmodule-2.0.so.0 from rpm glib2-2.78.3-1.fc39.x86_64
Module libXau.so.6 from rpm libXau-1.0.11-3.fc39.x86_64
Module libplds4.so from rpm nss-3.98.0-1.fc39.x86_64
Module libplc4.so from rpm nss-3.98.0-1.fc39.x86_64
Module libpcre2-8.so.0 from rpm pcre2-10.42-1.fc39.2.x86_64
Module libffi.so.8 from rpm libffi-3.4.4-4.fc39.x86_64
Module libdrm.so.2 from rpm libdrm-2.4.120-1.fc39.x86_64
Module libatspi.so.0 from rpm at-spi2-core-2.50.2-1.fc39.x86_64
Module libcups.so.2 from rpm cups-2.4.7-11.fc39.x86_64
Module libpango-1.0.so.0 from rpm pango-1.51.0-1.fc39.x86_64
Module libpangocairo-1.0.so.0 from rpm pango-1.51.0-1.fc39.x86_64
Module libasound.so.2 from rpm alsa-lib-1.2.11-2.fc39.x86_64
Module libdbus-1.so.3 from rpm dbus-1.14.10-1.fc39.x86_64
Module libexpat.so.1 from rpm expat-2.6.2-1.fc39.x86_64
Module libXrandr.so.2 from rpm libXrandr-1.5.4-1.fc39.x86_64
Module libgio-2.0.so.0 from rpm glib2-2.78.3-1.fc39.x86_64
Module libXtst.so.6 from rpm libXtst-1.2.4-3.fc39.x86_64
Module libXrender.so.1 from rpm libXrender-0.9.11-3.fc39.x86_64
Module libXi.so.6 from rpm libXi-1.8.1-2.fc39.x86_64
Module libXfixes.so.3 from rpm libXfixes-6.0.0-6.fc39.x86_64
Module libXext.so.6 from rpm libXext-1.3.5-3.fc39.x86_64
Module libXdamage.so.1 from rpm libXdamage-1.1.5-10.fc39.x86_64
Module libXcursor.so.1 from rpm libXcursor-1.2.1-4.fc39.x86_64
Module libXcomposite.so.1 from rpm libXcomposite-0.4.5-10.fc39.x86_64
Module libxcb-dri3.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libxcb.so.1 from rpm libxcb-1.13.1-12.fc39.x86_64
Module libX11-xcb.so.1 from rpm libX11-1.8.7-1.fc39.x86_64
Module libatk-bridge-2.0.so.0 from rpm at-spi2-core-2.50.2-1.fc39.x86_64
Module libatk-1.0.so.0 from rpm at-spi2-core-2.50.2-1.fc39.x86_64
Module libnspr4.so from rpm nss-3.98.0-1.fc39.x86_64
Module libglib-2.0.so.0 from rpm glib2-2.78.3-1.fc39.x86_64
Module libgobject-2.0.so.0 from rpm glib2-2.78.3-1.fc39.x86_64
Module libX11.so.6 from rpm libX11-1.8.7-1.fc39.x86_64
Stack trace of thread 61894:
#0 0x00007f804b403824 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x1c03824)
#1 0x00007f804b406d1d n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x1c06d1d)
#2 0x00007f804b40c3ea n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x1c0c3ea)
#3 0x00007f804bb7e4db n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x237e4db)
#4 0x00007f804bb83ab6 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x2383ab6)
#5 0x00007f804bb85b78 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x2385b78)
#6 0x00007f804bb8730f n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x238730f)
#7 0x00007f804f105b07 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x5905b07)
#8 0x00007f804ec98914 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x5498914)
#9 0x00007f804ec9c85d n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x549c85d)
#10 0x00007f804ecb185e n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x54b185e)
#11 0x00007f804ecb171c n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x54b171c)
#12 0x00007f804ec9fd18 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x549fd18)
#13 0x00007f804eb4e3e2 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x534e3e2)
#14 0x00007f804c76dfe1 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x2f6dfe1)
#15 0x00007f804c76a3c0 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x2f6a3c0)
#16 0x00007f804c76b8da n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x2f6b8da)
#17 0x00007f804f32a77b n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x5b2a77b)
#18 0x00007f804dc132a6 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x44132a6)
#19 0x00007f804dc23cec n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x4423cec)
#20 0x00007f804dbdcb9a n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x43dcb9a)
#21 0x00007f804dc243b4 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x44243b4)
#22 0x00007f804dbfbf6e n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x43fbf6e)
#23 0x00007f805282d5a2 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x902d5a2)
#24 0x00007f804da66fca n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x4266fca)
#25 0x00007f804da68172 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x4268172)
#26 0x00007f80503dd2bf n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x6bdd2bf)
#27 0x00007f80503dd80e n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x6bdd80e)
#28 0x00007f804da664a1 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x42664a1)
#29 0x00007f804daf8aac n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x42f8aac)
#30 0x00007f804dad1fcd n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x42d1fcd)
#31 0x00007f804b2ecd1a n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/libcef.so + 0x1aecd1a)
#32 0x000055d51e4f60e4 n/a (/home/crashdummy/.local/share/Steam/steamapps/common/SteamVR/bin/vrwebhelper/linux64/vrwebhelper + 0x1360e4)
ELF object binary architecture: AMD x86-64
Replying to #667 (comment)
This was all in Wayland. Switching to X11, SteamVR beta 2.5.1 opens and works, but I can't open certain games. I click play and it thinks for maybe 3-5 seconds before the button just goes back to play, and the game never opens. This behavior is happening with Jet Island and Hot Dogs, Horseshoes & Hand Grenades, but not with Escape Simulator VR Demo. I was able to play H3VR yesterday. This persisted when I switched back to Wayland too. Not sure if something changed between today and yesterday, or if switching to X11 caused this. X11 report: SteamVR-2024-04-09-PM_05_37_18.txt
Switching back to stable 2.4.4: SteamVR and launching and playing all games is working in Wayland and X11.
Well your luck is not mine. absolutely nothing changed on my ends I even reinstalled Fedora and nothing changed, I updated to fedora 40 and also nothing has changed. Using the old Linux version 1.14 while unstable kind of works but I'm getting a timeout response from Mongoose when I try Half-Life Alyx
This seems to be at least mostly only on fedora wayland. This has been going on for a long time which is really really annoying. You'd think after months of complaints in multiple issue threads they'd at least run a test on Fedora and acknowledge the bug lol.
Still an issue here on Fedora 39 x86_64 with X11 and NVIDIA. Yes, I checked my cables. Yes, I rebooted, with and without the cables attached. I tried SteamVR Stable, Beta, and the old version for Linux under Beta builds. None of these work.
I can play just about anything else on my Fedora Linux PC, just not SteamVR.
@carlbennett @makinbacon21
I dont know if your case is the same but I can safely ignore those vrwebhelper segfaults. I use a meta quest 3 using the ALVR project.
While I still get a 109 when I start steamvr through steam it appears to be working when I start steam + steamvr through the "Launch SteamVR" button on the ALVR Dashboard.
Tested on Gnome, KDE with Fedora 39 and nobara 39 on wayland and X11 ( even using hybrid on my laptop )
@carlbennett @makinbacon21
I dont know if your case is the same but I can safely ignore those vrwebhelper segfaults. I use a meta quest 3 using the ALVR project.
While I still get a 109 when I start steamvr through steam it appears to be working when I start steam + steamvr through the "Launch SteamVR" button on the ALVR Dashboard.
Tested on Gnome, KDE with Fedora 39 and nobara 39 on wayland and X11 ( even using hybrid on my laptop )
Vive Pro Eye 1st gen., so I do not have a Quest.
The headset turns on with a gray screen in both eyes, that's about as far as I can get it. It won't track on the base stations even if SteamVR sees the headset, stations, and controllers as connected devices. Steam's vrwebhelper crashing makes SteamVR unusable to do anything except Launch. If I put on the headset with say, Beat Saber running while SteamVR is broken, it remains gray. Sometimes the headset doesn't even turn on the eyes, but has a red dot LED indicating it's on but the displays are not.
Every 5 months or so I try to test the Indexes (for HLA), in the end they are all errors. Now error 109
i fixed my problem by updating my system, (artix) and reinstalling steam, also make sure you have the lib32 libraries, i got a pop up that gave me a list of libs and i got them, heres the list:
after that i still did not get the steam dashboard working but SteamVR Home worked and i can now launch games.
Throwing my hat into the ring:
My setup: Fedora 40, KDE Plasma 6, Wayland AMD CPU, AMD GPU Valve Index SteamVR Beta: 2.5.3 Steam Client Beta (latest 1714520927)
Getting the same 109 and 497 errors as everyone else.
Launched SteamVR with launch options: steam-runtime-launch-options -- %command%
Getting a pop-up window:
If I click "Run", I will get the same errors as before, but if I copy the command text next to "Preview of final command" to a terminal (Konsole in my case), SteamVR will start without 109 and 497 and I get a picture in my headset.
I also noticed that if I select "Interactive Terminal" and choose "Run in Xterm" (had to install Xterm first), I get the same errors and I see a message in the terminal saying that "vrsetup.sh[47608]: Relaunching under scout LDLP runtime."
So it's not using the sniper runtime? Here's the code snippet from Xterm:
vrstartup.sh[47573]: Relaunch under vrenv.
vrstartup.sh[47573]: exec /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup.sh
vrenv.sh[47573]: VRCOMPOSITOR_LD_LIBRARY_PATH=/home/fedoragame/.local/share/Steam/steamapps/common/SteamVR:/home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/linux64:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases
vrenv.sh[47573]: exec /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup.sh
vrstartup.sh[47573]: Steam Linux Runtime: sniper_platform_0.20240423.85483
vrstartup.sh[47573]: call /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrsetup.sh
vrsetup.sh[47600]: Detected Steam Linux Runtime pressure-vessel launch in sniper_platform_0.20240423.85483
vrsetup.sh[47600]: Relaunching via steam launcher service to host level for vrcompositor setcap configuration.
vrsetup.sh[47608]: exec /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrenv.sh /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrsetup.sh
vrenv.sh[47608]: VRCOMPOSITOR_LD_LIBRARY_PATH=/home/fedoragame/.local/share/Steam/steamapps/common/SteamVR:/home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/qt/lib:/home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/linux64:
vrenv.sh[47608]: exec /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrsetup.sh
vrsetup.sh[47608]: Relaunching under scout LDLP runtime.
vrsetup.sh[47608]: exec /home/fedoragame/.steam/bin/steam-runtime/run.sh /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrsetup.sh
vrsetup.sh[47608]: Detected scout LDLP runtime.
vrsetup.sh[47608]: /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher binary has cap_sys_nice privileges
vrstartup.sh[47573]: exec /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup-helper.sh
vrstartup-helper.sh[47573]: exec /home/fedoragame/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrstartup
Also weird that all other SteamVR versions (1.27.5 beta) and SteamVR 2.4.4 (non-beta) don't have any Container Runtime settings at all, when launching with steam-runtime-launch-options -- %command%
You can choose the Runtime Container manually along side with the Variable Data Path (/home/fedoragame/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/var) in my case and I can get other versions of SteamVR startup as well.
Hello,
Thank you for your report. steam-runtime-launch-options
is not a Valve tool, I don't know what it is but I can only guess it's going to cause more problems than it will fix.
Please review the bug report guidelines at https://github.com/ValveSoftware/SteamVR-for-Linux/blob/master/issue_template.md and provide the requested logs and crash dumps when testing on an unmodified system so that we can investigate.
Nevermind, it's something from us but I don't see any reason you'd want to use it. Please make sure to test from latest SteamVR beta and launch SteamVR from the Steam client without command line edits.
This is a very strange response to an issue ongoing since December...the operable issue for all of us is clearly the same, and it has not been addressed. The program he is using to adjust runtime launch options is irrelevant given we have all tried it without any extras and it does not work. The issue, as far as I can tell, follows the template. In case the logs, reports, and many people corroborating the same story are not enough, I've added below the logs requested by the template:
System: Fedora 40 Steam Client (beta): 1714160074 SteamVR (beta): 2.5.3 steam-logs.tar.gz steam-minidumps.tar.gz
Sometimes users try to mess with commandline arguments to see if they can bypass issues. For instance, I briefly was able to bypass the issue a couple times with a couple of radeon- and wayland-related flags, but it was not a permanent or reliable solution. It seems weird for the company to finally reply to the thread months later to point out the most recent of many, many comments isn't using a fully clean environment.
Hello @makinbacon21,
Thank you for your report.
vrcompositor.txt
ends with:
Thu May 02 2024 21:17:00.221846 [Info] - Mirror swapchain mode:0 count:5
Thu May 02 2024 21:17:00.222056 [Info] - Swapchain failed to be created: ffffffff
Thu May 02 2024 21:17:00.222076 [Error] - CHmdWindowSDL::CreateSwapChainBufferResources - Invalid swapchain
Thu May 02 2024 21:17:00.222138 [Error] - CHmdWindowSDL: Failed to initialize mirror window
Thu May 02 2024 21:17:00.222233 [Error] - Error making window!
This suggests a problem with your vulkan drivers. Could be misconfiguration, unsupported driver, unsupported hardware .. I don't know at this time.
Unfortunately you haven't provided the requested Steam runtime diagnostics (generate via Help -> Steam Runtime Diagnostics in the Steam client) so I cannot follow up further. Please consider providing that too.
The provided logs did highlight a bug on our end with the packaging of SteamVR 2.5.3 though, to fix you can update files in SteamVR's bin/ folder: steamvr-2.5.3-startup-script-fixes.tar.gz
It's shown in the above but I'm using a 7900XTX with default amdgpu drivers on Fedora 40.
Here are also my logs, minidumps and runtime-diagnostics. Apologies for not including them eariler. I do understand that consistent reporting is important. The reason why I started tinkering with steam-runtime-launch-options
was, because I saw some people having success in another thread with it.
Also, a couple of questions for the person, who wrote the program "steam-runtime-launch-options", if they are still working at Valve:
If I launch SteamVR with launch option steam-runtime-launch-options -- %command%
and in the pop-up window, I don't change anything and just click "Run", is that the same as running SteamVR without any launch-options?
When launching SteamVR with above launch options, is the Run-button supposed to run the exact same command that is written in the "Preview of final command"? If so, then is it possible that the Run button is omitting some environment variable from the launch command or why does it work, when I copy the launch command to a terminal and SteamVR that way?
These below are run without any launch options.
My system info:
Steam client version: 1714520927 SteamVR version: 2.5.3 beta Distribution: Fedora 40, KDE Plasma 6, Wayland CPU: AMD 5800X3D GPU: AMD Radeon 6800XT
steam-logs.tar.gz steam-minidumps.tar.gz Steam-runtime-diagnostics.txt
https://pastebin.com/751YFWfc It's shown in the above but I'm using a 7900XTX with default amdgpu drivers on Fedora 40.
Looks like a dead link, I can't load the pastebin.
sorry, pastebin sucks. https://hastebin.com/share/irimivugid.kotlin (not sure why it thinks it's kotlin but whatever)
With the provided fixes, same issue happens but more consistently gets the seemingly more helpful "Failed to connect to window manager" error. It also actually prompts me for sudo instead of before where it wouldn't bother and steam logs would just print that that failed. Anyway here are the logs with the fixes.
steam-logs.tar.gz steam-minidumps.tar.gz https://hastebin.com/share/uvasojuhar.kotlin
Still playing around with this. Looks to me, that SDL_VIDEODRIVER=x11
is the solution in my case, but that environment variable isn't picked up, when putting it in the launch options of SteamVR.
I can only force it in a terminal, when launching SteamVR like this:
SDL_VIDEODRIVER=x11 ~/.local/share/Steam/ubuntu12_32/reaper SteamLaunch AppId=250820 -- ~/.local/share/Steam/ubuntu12_32/steam-launch-wrapper -- ~/.local/share/Steam/steamapps/common/SteamLinuxRuntime_sniper/_v2-entry-point --verb=waitforexitandrun -- ~/.local/share/Steam/steamapps/common/SteamVR/bin/vrstartup.sh
If I change SDL_VIDEODRIVER=wayland on the terminal command, then I get errors 109 and 497 and no image in headset.
Emptied log folder (.local/share/Steam/logs/) and exited and relaunched Steam client before launching commands on the terminal.
Minidumps didn't produce anything new, while doing this experiment, but there are enties in the "completed"-folder. steam-minidumps.tar.gz
@wallcarpet40's fix is correct, SDL_VIDEODRIVER=x11
needs to be set in the vrcompositor
launch options.
This shouldn't be needed, but it turns out Fedora has changed SDL's default behavior from the official SDL release.
We will fix this in a SteamVR update, you should be able to edit linux64/vrcompositor-launcher.sh
and add a line with export SDL_VIDEODRIVER=x11
to fix this for now.
@wallcarpet40 also, the way you are trying to launch SteamVR from the command line is going to be problematic for other reasons.
In order to launch SteamVR from the CLI, you can do the following with the Steam client running:
timo@vanguard ~/.s/s/s/c/S/bin> pwd
/home/timo/.steam/steam/steamapps/common/SteamVR/bin
timo@vanguard ~/.s/s/s/c/S/bin> SRT_LAUNCHER_SERVICE_ALONGSIDE_STEAM=1 ~/.steam/steam/steamapps/common/SteamLinuxRuntime_sniper/run-in-sniper ./vrstartup.sh
(you will need to edit vrcompositor-launcher.sh
as explained above first though)
OK so that launches but room setup does not work and it waits indefinitely. I also attempted with the flag exported in the room setup script--now it no longer spawns a broken window but nothing is spawned at all which is similarly unhelpful.
Logs: steam-logs.tar.gz steam-minidumps.tar.gz https://hastebin.com/share/opewehexew.kotlin
SteamVR does launch now, after putting export SDL_VIDEODRIVER=x11
in the vrcompositor-launcher.sh
but like @makinbacon21 said, room setup won't work and in my case, it also disables the Dashboard completely. I don't see any instances of vrwebhelper
in System Monitor's process list.
A positive side effect though is that since the Dashboard is disabled, the performance of games went up as vrwebhelper
is not consuming a lot of CPU any more and not constantly writing to disk at 8MB/s.
Different behaviour, if I put export SDL_VIDEODRIVER=x11
in vrenv.sh
instead of vrcompositor-launcher.sh
. SteamVR launches, the Dashboard now works, no Room Setup though.
Please open separate issues (or find existing/corresponding ones) for the other problems (room setup etc.). I plan to close this issue once the fix ships.
Linux:
Fixed an SDL compatibility problem on Fedora.
Have not tested this myself yet, but the latest beta states this should now be fixed.
This continues to be an issue on 2.5.4. On first launch it opened but Room Setup was broken and nothing showed from display, and on a reboot it has the exact same issue again. https://hastebin.com/share/afofoniheq.kotlin
See https://github.com/ValveSoftware/SteamVR-for-Linux/issues/694 for the room setup problem. The SDL_VIDEODRIVER=x11
fix has shipped, closing this.
Describe the bug SteamVR failed to initialize for unknown reasons. (Error: Not Initialized (109)(109)) A key component of SteamVR isn't working properly. Please quit SteamVR, then visit Task Manager and End any remaining SteamVR tasks before restarting the app. (307)
SteamVR will crash every time I attempt to launch it. The HMD does not light up. Sometimes it will crash entirely, where vrmonitor will close and the launch button is green and launchable again, sometimes vrmonitor will stay open, but still crashed (the menus are usable and the launch button is blue and shows stop, but the VR component is still crashed and the HMD is dark).
The Not Initialized (109) error always appears, and typically will appear twice after clicking launch.
The above is all with Manjaro's
steam
package, launched with Steam (Runtime). With the Flatpak Steam, VR does appear to work as expected on stable 2.2.3, but does not launch at all on beta 2.2.4. No errors are reported, and no logs are generated in~/.var/app/com.valvesoftware.Steam/data/Steam/logs/
.To Reproduce Steps to reproduce the behavior:
Expected behavior SteamVR launches without errors; VR environment viewable through HMD.
System Information (please complete the following information):
Screenshots
Additional Context
Also of possible note, Steam's System Information reports VR Headset as None detected, even while SteamVR is open and showing my Index as green and detected.
Note: Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.