Linux - SteamVR enters direct display mode since the latest SteamVR update

[CrazyVito11]

Description

It seems like the latest SteamVR update broke ALVR for Linux, as it now thinks it needs to go to direct display mode. In the headset it doesn't show any picture, and the statistics screen is also stuck.

I'm not completely sure if this is a bug on the ALVR side or SteamVR, sadly my technical knowledge about both of them is very limited. If this is suspected to be a SteamVR bug, please let me know and then I'll create an issue for SteamVR.

If I go back to the old SteamVR version _(linuxv1.14), it launches properly again. But on the latest stable or beta release, it goes to direct display mode.

General Troubleshooting

• [x] I carefully followed the instructions in the README and successfully completed the setup wizard
• [x] I read the ALVR Wikis here and here

ALVR has worked on this system before, last tested around 2 days ago. SteamVR was updated yesterday, so something in that update probably broke something. The older linux_v1.14 release does work properly.

Environment

Hardware

Note: for Linux, an upload to the hw-probe database is preferred: hw-probe -all -upload

CPU: AMD Ryzen 7 5700X

GPU: AMD Radeon RX 7900XTX

GPU Driver Version: 23.1.3

Audio: Pipewire

Installation

ALVR Version: 20.1.0

ALVR Settings File: session.json.txt

SteamVR Version: 1.26

Install Type:

• [x] Packaged (exe, deb, rpm, etc)
• [ ] Portable (zip)
• [ ] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions): Arch Linux (KDE Plasma running on Wayland)

[Vixea]

Do not go back to Linux 1.14

[Vixea]

WAYLAND_DISPLAY='' %command% is required in commandline options for steamvr to work with Wayland and alvr on most DEs (like gnome, hyprland) and until drm leasing gets added in a nightly kde

[CrazyVito11]

Adding WAYLAND_DISPLAY='' %command% seems to have fixed the issue for me, thanks!