search

ValveSoftware / SteamVR-for-Linux

Issue tracker for the Linux port of SteamVR
921 stars 45 forks source link

[BUG] Failed to connect to headset display (496) #636

Open Martmists-GH opened 11 months ago

Martmists-GH commented 11 months ago

Describe the bug It seems to fail to connect no matter what I try.

To Reproduce Steps to reproduce the behavior:

  1. Connect headset
  2. Click "Enter VR Mode"

Expected behavior VR works as expected

System Information (please complete the following information):

Screenshots N/A

Additional context I'm also experiencing issues with xrdesktop crashing with the following:

dbus property change: true
vrcompositor-launcher.sh[175844]: === Thu Nov  9 06:22:52 PM CET 2023 ===
vrcompositor-launcher.sh[175844]: Relaunch under scout LDLP runtime.
vrcompositor-launcher.sh[175844]: exec /home/mart/.steam/root/ubuntu12_32/steam-runtime/run.sh /home/mart/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher.sh
vrcompositor-launcher.sh[175844]: Detected scout LDLP runtime.
vrcompositor-launcher.sh[175844]: exec /home/mart/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor-launcher
Using vrcompositor capability proxy
Failed to raise ambient cap
Launching /home/mart/.local/share/Steam/steamapps/common/SteamVR/bin/linux64/vrcompositor
Using breakpad crash handler
Setting breakpad minidump AppID = 250820
Forcing breakpad minidump interfaces to load
Looking up breakpad interfaces from steamclient
Calling BreakpadMiniDumpSystemInit
11/09 18:22:52 Init: Installing breakpad exception handler for appid(250820)/version(2.0.10)/tid(175844)

** (process:175800): WARNING **: 18:22:52.946: [XR_ERROR_RUNTIME_FAILURE] Failed to create session
Could not init VR session.

** (process:175800): WARNING **: 18:22:52.953: Failed to create gxr context, unable to create g3k context
Could not init VR runtime.
Failed to initialize xrdesktop!
Usually this is caused by a problem with the VR runtime.

though I'm not sure if this is related or not.

Darth-Ender commented 10 months ago

I'm getting this error in debian unstable as well. Beta steamvr, normal steamvr, beta client, normal client. In wayland and in Xorg. Nothing i try seems to want to let things work like they used to with my Vive.

I dont have xrdesktop errors and such, just the 496 can't connect to headset / headset not found error from what it looks like. Nothing else seems to stand out error-wise.

kernel is 6.6 Mesa 23.2.1

Not sure what other info is relevant. everything worked perfectly like a month ago.

Darth-Ender commented 10 months ago

FYI, i resolved the connecting to headset issue by replacing the 3-in-1 cable on the headset. My issue was definitely the HDMI cable the headset uses. Swapping a different hdmi cable brought it right back.

You can verify if this issue is your issue by using xrandr (even in wayland). if the second display doesn't show 2160x1200 as a detected resolution (or it shows almost nothing at all or nothing at all) ..then it's likely the hdmi cable has degraded to the point of not being functional.

diademiemi commented 10 months ago

I'm still getting the issue and the xrandr output seems fine. It worked 2 days ago, Fedora 39 with Steam beta and Steam VR beta

I'm on Wayland and see the following in vrcompositor.txt in ./local/share/Steam/logs

Logs ``` Sat Nov 11 2023 20:29:55.682889 [Info] - [Settings] Load Json Settings from /home/diademiemi/.local/share/Steam/config/steamvr.vrsettings Sat Nov 11 2023 20:29:55.683756 [Info] - Events created Sat Nov 11 2023 20:29:55.684139 [Info] - Found bad mirror window settings: Sat Nov 11 2023 20:29:55.684153 [Info] - Creating CHmdWindowSDL! Sat Nov 11 2023 20:29:55.684185 [Info] - CHmdWindowSDL: Using Wayland Sat Nov 11 2023 20:29:55.730821 [Info] - WaylandHMDState: Got interface: wp_drm_lease_device_v1 Sat Nov 11 2023 20:29:55.730860 [Info] - WaylandHMDState: Got interface: wp_drm_lease_device_v1 Sat Nov 11 2023 20:29:55.731882 [Error] - WaylandHMDLeaseDevice::LeaseDevice_DrmFD: No libdrm.so Sat Nov 11 2023 20:29:55.731896 [Info] - WaylandHMDLeaseDevice::LeaseDevice_DrmFD: (null) Sat Nov 11 2023 20:29:55.731911 [Info] - WaylandHMDLeaseDevice::LeaseDevice_Done Sat Nov 11 2023 20:29:55.731920 [Error] - WaylandHMDLeaseDevice::LeaseDevice_DrmFD: No libdrm.so Sat Nov 11 2023 20:29:55.731929 [Info] - WaylandHMDLeaseDevice::LeaseDevice_DrmFD: (null) Sat Nov 11 2023 20:29:55.731943 [Info] - WaylandHMDLeaseConnector::LeaseConnector_Done Sat Nov 11 2023 20:29:55.731962 [Info] - WaylandHMDLeaseDevice::LeaseDevice_Done Sat Nov 11 2023 20:29:55.732754 [Info] - Instance layers available: Sat Nov 11 2023 20:29:55.732768 [Info] - - VK_LAYER_VALVE_steam_fossilize_32, version 4206799 Sat Nov 11 2023 20:29:55.732777 [Info] - - VK_LAYER_VALVE_steam_overlay_64, version 4206799 Sat Nov 11 2023 20:29:55.732786 [Info] - - VK_LAYER_VALVE_steam_overlay_32, version 4206799 Sat Nov 11 2023 20:29:55.732794 [Info] - - VK_LAYER_VALVE_steam_fossilize_64, version 4206799 Sat Nov 11 2023 20:29:55.732803 [Info] - - VK_LAYER_MESA_device_select, version 4206803 Sat Nov 11 2023 20:29:55.733877 [Info] - Instance extensions available: Sat Nov 11 2023 20:29:55.733892 [Info] - - VK_KHR_device_group_creation, version 1 Sat Nov 11 2023 20:29:55.733901 [Info] - - VK_KHR_external_fence_capabilities, version 1 Sat Nov 11 2023 20:29:55.733910 [Info] - - VK_KHR_external_memory_capabilities, version 1 Sat Nov 11 2023 20:29:55.733918 [Info] - - VK_KHR_external_semaphore_capabilities, version 1 Sat Nov 11 2023 20:29:55.733927 [Info] - - VK_KHR_get_physical_device_properties2, version 2 Sat Nov 11 2023 20:29:55.733936 [Info] - - VK_KHR_get_surface_capabilities2, version 1 Sat Nov 11 2023 20:29:55.733944 [Info] - - VK_KHR_surface, version 25 Sat Nov 11 2023 20:29:55.733953 [Info] - - VK_KHR_surface_protected_capabilities, version 1 Sat Nov 11 2023 20:29:55.733961 [Info] - - VK_KHR_wayland_surface, version 6 Sat Nov 11 2023 20:29:55.733970 [Info] - - VK_KHR_xcb_surface, version 6 Sat Nov 11 2023 20:29:55.733978 [Info] - - VK_KHR_xlib_surface, version 6 Sat Nov 11 2023 20:29:55.733987 [Info] - - VK_EXT_debug_report, version 10 Sat Nov 11 2023 20:29:55.733995 [Info] - - VK_EXT_debug_utils, version 2 Sat Nov 11 2023 20:29:55.734004 [Info] - - VK_KHR_display, version 23 Sat Nov 11 2023 20:29:55.734018 [Info] - - VK_KHR_get_display_properties2, version 1 Sat Nov 11 2023 20:29:55.734028 [Info] - - VK_EXT_acquire_drm_display, version 1 Sat Nov 11 2023 20:29:55.734036 [Info] - - VK_EXT_acquire_xlib_display, version 1 Sat Nov 11 2023 20:29:55.734045 [Info] - - VK_EXT_direct_mode_display, version 1 Sat Nov 11 2023 20:29:55.734053 [Info] - - VK_EXT_display_surface_counter, version 1 Sat Nov 11 2023 20:29:55.734062 [Info] - - VK_EXT_surface_maintenance1, version 1 Sat Nov 11 2023 20:29:55.734070 [Info] - - VK_EXT_swapchain_colorspace, version 4 Sat Nov 11 2023 20:29:55.734079 [Info] - - VK_KHR_portability_enumeration, version 1 Sat Nov 11 2023 20:29:55.734087 [Info] - - VK_LUNARG_direct_driver_loading, version 1 Sat Nov 11 2023 20:29:55.734099 [Info] - SDL version: 2.28.4 Sat Nov 11 2023 20:29:55.734110 [Info] - Direct mode features: present Sat Nov 11 2023 20:29:55.734119 [Info] - Requesting 9 instance extensions: Sat Nov 11 2023 20:29:55.734128 [Info] - - VK_KHR_surface Sat Nov 11 2023 20:29:55.734136 [Info] - - VK_KHR_xlib_surface Sat Nov 11 2023 20:29:55.734145 [Info] - - VK_KHR_display Sat Nov 11 2023 20:29:55.734153 [Info] - - VK_EXT_direct_mode_display Sat Nov 11 2023 20:29:55.734162 [Info] - - VK_EXT_display_surface_counter Sat Nov 11 2023 20:29:55.734170 [Info] - - VK_KHR_external_memory_capabilities Sat Nov 11 2023 20:29:55.734179 [Info] - - VK_KHR_external_semaphore_capabilities Sat Nov 11 2023 20:29:55.734188 [Info] - - VK_KHR_get_physical_device_properties2 Sat Nov 11 2023 20:29:55.734200 [Info] - - VK_EXT_acquire_drm_display Sat Nov 11 2023 20:29:55.742556 [Info] - HMD deviceUUID is 1200000000 Sat Nov 11 2023 20:29:55.742915 [Warning] - CHmdWindowSDL::FindDirectDisplayWayland: vkGetDrmDisplay failed. Sat Nov 11 2023 20:29:55.743267 [Warning] - CHmdWindowSDL::FindDirectDisplayWayland: vkGetDrmDisplay failed. Sat Nov 11 2023 20:29:55.743607 [Warning] - CHmdWindowSDL::FindDirectDisplayWayland: vkGetDrmDisplay failed. Sat Nov 11 2023 20:29:55.743940 [Warning] - CHmdWindowSDL::FindDirectDisplayWayland: vkGetDrmDisplay failed. Sat Nov 11 2023 20:29:55.743949 [Info] - Tried to find direct display through Wayland: (nil) Sat Nov 11 2023 20:29:55.743958 [Error] - CHmdWindowSDL: Failed to create direct mode surface Sat Nov 11 2023 20:29:55.744014 [Error] - CHmdWindowSDL: VR requires direct mode. Sat Nov 11 2023 20:29:55.744079 [Error] - Error making window! Sat Nov 11 2023 20:29:55.795409 [Info] - Failed to kill gpu-trace Sat Nov 11 2023 20:29:55.795517 [Info] - Failed to initialize compositor Sat Nov 11 2023 20:29:55.795535 [Info] - Failed to start compositor: VRInitError_Compositor_CannotDRMLeaseDisplay ```
diademiemi commented 10 months ago

After further investigation I think it's a hardware issue for me too, I just reached out to customer support

diademiemi commented 10 months ago

After more troubleshooting, adding https://github.com/ValveSoftware/steam-devices/blob/master/60-steam-vr.rules to /etc/udev/rules.d fixed the issue. Very strange how it worked for a day without them

Darth-Ender commented 10 months ago

I purchased a new 3 in one cable. The display worked for a day. Then back to not working. edid decode data looks the same as any others i've been able to find online. I tried manually adding the mode in xrandr that the vive uses but no dice there. I've got no idea why this is not working after working just fine for so long. Unless there is some other underlying hardware or amd firmware issue. I even added the udev rules linked above and still zip.

Debian unstable Xorg: 21.1.9 vulkan: 1.3.268 glx: AMD Radeon RX 7900 XT (gfx1100, LLVM 16.0.6, DRM 3.56, 6.7.0-rc2 (tried in X and wayland 1.22.0-2.1 (kde plasma ))

I keep coming to this issue with xrandr not being able to see the expected mode. (vive is on output 0x53) vrcompositor.txt Thu Nov 23 2023 16:39:36.976210 [Info] - Looking for direct display through RandR Thu Nov 23 2023 16:39:36.976220 [Info] - - Root 0x6ce Thu Nov 23 2023 16:39:36.981920 [Info] - - Output 0x52 - 44 modes, 1 preferred Thu Nov 23 2023 16:39:36.981940 [Info] - - Mode 0 0x57 2560x1440 (looking for 2160x1200) Thu Nov 23 2023 16:39:36.981959 [Info] - - Output 0x53 - 6 modes, 0 preferred Thu Nov 23 2023 16:39:36.981976 [Info] - - Output 0x54 - 0 modes, 0 preferred Thu Nov 23 2023 16:39:36.981993 [Info] - - Output 0x55 - 0 modes, 0 preferred Thu Nov 23 2023 16:39:36.982000 [Info] - Tried to find direct display through RandR: (nil) Thu Nov 23 2023 16:39:36.982005 [Info] - Looking for direct display through Vulkan WSI Thu Nov 23 2023 16:39:36.982011 [Info] - Tried to find direct display through Vulkan WSI: (nil)

Below is the dmesg output related to amdgpu.

[ 1.097925] [drm] amdgpu kernel modesetting enabled. [ 1.100352] amdgpu: Virtual CRAT table created for CPU [ 1.100358] amdgpu: Topology: Add CPU node [ 1.100463] amdgpu 0000:0c:00.0: enabling device (0006 -> 0007) [ 1.104857] amdgpu 0000:0c:00.0: amdgpu: Fetched VBIOS from VFCT [ 1.104859] amdgpu: ATOM BIOS: 113-D70201-810006 [ 1.104983] amdgpu 0000:0c:00.0: amdgpu: CP RS64 enable [ 1.105111] amdgpu 0000:0c:00.0: [drm:0xffffffffc0309296] JPEG decode is enabled in VM mode [ 1.105237] amdgpu 0000:0c:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 1.105255] amdgpu 0000:0c:00.0: amdgpu: MEM ECC is not presented. [ 1.105255] amdgpu 0000:0c:00.0: amdgpu: SRAM ECC is not presented. [ 1.105265] amdgpu 0000:0c:00.0: amdgpu: VRAM: 20464M 0x0000008000000000 - 0x00000084FEFFFFFF (20464M used) [ 1.105267] amdgpu 0000:0c:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF [ 1.105329] [drm] amdgpu: 20464M of VRAM memory ready [ 1.105330] [drm] amdgpu: 32108M of GTT memory ready. [ 1.105720] amdgpu 0000:0c:00.0: amdgpu: Will use PSP to load VCN firmware [ 1.317926] amdgpu 0000:0c:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 1.317929] amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 1.317961] amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x0000003d, smu fw if version = 0x0000003f, smu fw program = 0, smu fw version = 0x004e6601 (78.102.1) [ 1.317967] amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched [ 1.499276] amdgpu 0000:0c:00.0: amdgpu: SMU is initialized successfully! [ 3.327727] amdgpu 0000:0c:00.0: [drm:0xffffffffc030941b] JPEG decode initialized successfully. [ 3.328979] kfd kfd: amdgpu: Allocated 3969056 bytes on gart [ 3.328993] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1 [ 3.329015] amdgpu: Virtual CRAT table created for GPU [ 3.329289] amdgpu: Topology: Add dGPU node [0x744c:0x1002] [ 3.329292] kfd kfd: amdgpu: added device 1002:744c [ 3.329306] amdgpu 0000:0c:00.0: amdgpu: SE 6, SH per SE 2, CU per SH 8, active_cu_number 84 [ 3.329312] amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0 [ 3.329315] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 [ 3.329317] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 [ 3.329319] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0 [ 3.329321] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0 [ 3.329323] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0 [ 3.329325] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0 [ 3.329327] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0 [ 3.329329] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0 [ 3.329331] amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0 [ 3.329333] amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0 [ 3.329335] amdgpu 0000:0c:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8 [ 3.329337] amdgpu 0000:0c:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 8 [ 3.329339] amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 8 [ 3.329341] amdgpu 0000:0c:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0 [ 3.332435] amdgpu 0000:0c:00.0: amdgpu: Using BACO for runtime pm [ 3.332642] [drm] Initialized amdgpu 3.56.0 20150101 for 0000:0c:00.0 on minor 0

caseif commented 10 months ago

If it is a hardware issue in my case, it seems there's still a software component at play. I'm able to get the headset working on a separate Windows machine, but twice it gave a spurious message about the cable becoming disconnected at the headset, pressing the connection firmly resolved it though. Perhaps there's an issue with the hardware that SteamVR on Windows is somehow able to compensate for?

As a note, the headset does sometimes work on my Linux machine but it's seemingly at random. The udev rules didn't make any difference in my case.

Darth-Ender commented 10 months ago

i think I've resolved my issue by bypassing the link box for the hdmi connection. it might even be that the original cable was fine and it was always just the link box going bad. xrandr immediately showed all the correct resolutions and steamvr worked perfectly once bypassed.

2-3-5-41 commented 10 months ago

having this issue on a valve index, arch Linux, kde plasma wayland, latest kernel, steam client beta, steamvr (beta, and stable). I pray that the steamvr team leaves the "temp_v1.27.5" beta branch available until this is resolved...

caseif commented 9 months ago

I was encountering this issue intermittently in a Wayland session, then around a month ago it started occurring consistently in Wayland, then some time later it started occurring consistently in X11 as well. I found that renaming steamvr.vrsettings, opening SteamVR to generate a new one, closing SteamVR, and then restoring the original version solved the problem for me, at least for the time being.

Adamcake commented 9 months ago

Valve doesn't read their issue trackers, so posting here is akin to screaming into the void. Hopefully one day they'll hire their first ever competent developer. Until then at least, if someone finds a workaround for this, let me know.

Mon-Ouie commented 9 months ago

I'm a bit confused what happened, I experienced this issue for the first time ever today using my Index. The only thing I did since SteamVR last worked was I tried ALVR with a Quest 3 (I did make sure ~/.config/openvr/openvrpaths.vrpath was back to normal when switching back to using the Index).

Things I tried that did not work:

  1. Deleting steamvr.vrsettings
  2. Adding the udev rules
  3. Unplugging the Index (also I was able to run VR on Windows so I don't think the cable is faulty).
  4. Rebooting after doing each step

What did work eventually: switching from the normal branch to the 2.2.2 beta. I would then experience issue #638, but everything works after switching back to the main branch. I'm not sure if ALVR messed up some files in my installation or if it's a coincidence. Maybe try a clean reinstallation of SteamVR if you encounter this issue?

MegaShinySnivy commented 8 months ago

having this issue on a valve index, arch Linux, kde plasma wayland, latest kernel, steam client beta, steamvr (beta, and stable). I pray that the steamvr team leaves the "temp_v1.27.5" beta branch available until this is resolved...

I'm having the same issue. It only works under temp_v1.27.5, which tells me this isn't a hardware issue, its a software issue. Exact same setup too. The only way I could get it to work was that beta under x11, I had to ditch wayland. Also, any proton VR games (that is to say, all of them) crash steam on launch.

Darth-Ender commented 8 months ago

i think it's safe to say this error can be caused by a few different reasons. my issue was 100% hardware. bypassing the extension box for hdmi resolved my issue and i didn't need to ditch wayland or the latest version of everything that I'm using with my 7900xt.

On Mon, Feb 5, 2024, 11:23 PM MegaShinySnivy @.***> wrote:

having this issue on a valve index, arch Linux, kde plasma wayland, latest kernel, steam client beta, steamvr (beta, and stable). I pray that the steamvr team leaves the "temp_v1.27.5" beta branch available until this is resolved...

I'm having the same issue. It only works under temp_v1.27.5, which tells me this isn't a hardware issue, its a software issue. Exact same setup too. The only way I could get it to work was that beta under x11, I had to ditch wayland. Also, any proton VR games (that is to say, all of them) crash steam on launch.

— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/SteamVR-for-Linux/issues/636#issuecomment-1928920878, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFMX7A24UC2H4ALRQ3OCXDTYSHLADAVCNFSM6AAAAAA7E5SWRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYHEZDAOBXHA . You are receiving this because you commented.Message ID: @.***>

MegaShinySnivy commented 8 months ago

i think it's safe to say this error can be caused by a few different reasons. my issue was 100% hardware. bypassing the extension box for hdmi resolved my issue and i didn't need to ditch wayland or the latest version of everything that I'm using with my 7900xt.

Are you recommending we open a new issue then?

Crimsonize commented 3 months ago

I am having the exact same issue and none of the fixes listed for othere here are working for me.

Things I have tried:

  1. Deleting steamvr.vrsettings
  2. Adding the udev rules
  3. Unplugging the Index (also I was able to run VR on Windows just 5 days ago so I don't think the cable is faulty)
  4. Switching from the normal branch to the 2.6.2 beta
  5. Switching the Steam client to the stable branch from the families beta branch
  6. Rebooting after doing each step

System Information (please complete the following information):

Distribution: [Pop!_OS 22.04 LTS] SteamVR version: [SteamVR beta 2.6.2 (also tried the stable branch)] Steam client version: [1718395788 Steam Families Beta] Opted into Steam client beta?: [Yes (tried both with and without the beta)] Graphics driver version: [Nvidia 550.63] GPU ~ RTX 2080 TI, CPU ~ AMD® Ryzen 9 3900x 12-core processor × 24, MB ~ ROG Crosshair VIII Hero Gist for SteamVR System Information: https://gist.github.com/Crimsonize/a2eeab857b6af847b1478384b02f8778

Darth-Ender commented 2 months ago

the only way to be sure it's not a hardware problem is to swap in replacements until it starts working and isolate the part you need to replace or discover that it doesn't work if everything is replaced (which may indicate software issue)

my situation was hardware related. i bypass the extender box and plug the hdmi directly into my video card. also got a new triple cable.

On Sun, Jun 16, 2024, 6:59 AM Conor D @.***> wrote:

I am having the exact same issue and none of the fixes listed for othere here are working for me.

Things I have tried:

  1. Deleting steamvr.vrsettings
  2. Adding the udev rules
  3. Unplugging the Index (also I was able to run VR on Windows just 5 days ago so I don't think the cable is faulty)
  4. Switching from the normal branch to the 2.6.2 beta
  5. Switching the Steam client to the stable branch from the families beta branch
  6. Rebooting after doing each step

System Information (please complete the following information):

Distribution: [Pop!_OS 22.04 LTS] SteamVR version: [SteamVR beta 2.6.2 (also tried the stable branch)] Steam client version: [1718395788 Steam Families Beta] Opted into Steam client beta?: [Yes (tried both with and without the beta)] Graphics driver version: [Nvidia 550.63] GPU ~ RTX 2080 TI, CPU ~ AMD® Ryzen 9 3900x 12-core processor × 24, MB ~ ROG Crosshair VIII Hero Gist for SteamVR System Information: https://gist.github.com/Crimsonize/a2eeab857b6af847b1478384b02f8778

— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/SteamVR-for-Linux/issues/636#issuecomment-2171675013, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFMX7A4LG7AMNFJCRPTLS33ZHWK2PAVCNFSM6AAAAAA7E5SWRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGY3TKMBRGM . You are receiving this because you commented.Message ID: @.***>