protonscr

[BUG] In VR menu has corrupted graphics

steamvropen bug
ValveSoftware/SteamVR-for-Linux#640 · opened 2023-11-17 by velezd · updated 2026-04-07 · 10 comments · github
Vvelezd 2023-11-17 github

In VR menu has corrupted graphics. I can still launch games from Steam UI and they seem to be working fine.

Steps to reproduce the behavior:

  1. Start SteamVR
  2. Open menu
  3. See problem

System Information:

  • Distribution: Nobara Linux 38 (KDE Plasma)
  • SteamVR version: 2.0.10 (1698775809)
  • Steam client version: 1698777785
  • Opted into Steam client beta?: No
  • Graphics driver version:
    driverInfo = Mesa 24.0.0-devel
    mesa-vulkan-drivers-23.3.0-git.20231029.c4283e3.fc38.x86_64
    mesa-dri-drivers-23.2.1-1.fc38.x86_64
  • Gist for SteamVR System Information: https://gist.github.com/velezd/852d829ef93b4b7661b99424ccbc82dd

Screenshot

I have this problem for quite a long time. I updated kernel and drivers a few times without change.
When I try SteamVR beta the VR headset is not detected at all.

Commenters who are also experiencing this issue are encouraged to include the "System Information" section in their replies.

Ddevurandom 2024-03-20 github

Visuals on my system looks similar to yours, also corrupt with encoding / decoding errors and block artifacts, but only when in a game. It affects both the VR goggles and SteamVR's "VR view", so it seems more likely related to reading the game's output than to transferring the video stream to the goggles using ALVR.

Screenshot_20240320_204524

The "mountain range" backdrop works fine, as does the Steam UI when I click "toggle dashboard" in the SteamVR menu. Pressing the menu button while in a game also shows the Steam menu ("exit game" and other options) without any apparent issues.

I am using ALVR 20.6.1 with a Meta / Oculus Quest 2 and an AMD Radeon RX 6800S.

SteamVR System Report: https://gist.github.com/devurandom/c5bf7c7db42c33211f508cd8a017251f

KKishanPRao 2024-05-11 github

I have the same issue, the dashboard is always corrupted.
Switching versions/beta did not help.

I am using ALVR v20.8.1 with Meta / Oculus Quest 2 and AMD Radeon RX 6800M, running on Arch Linux, KDE Plasma (Wayland).

Ddevurandom 2024-06-04 github

as does the Steam UI when I click "toggle dashboard" in the SteamVR menu.

Currently this stopped working as well.

I am using ALVR 20.6.1

Same with ALVR 20.8.1 and SteamVR 2.6.2 (beta).

Ddevurandom 2024-06-04 github

Someone on the ALVR Discord also had the same problem:

They fixed their problem by running Steam with DRI_PRIME=1 (env DRI_PRIME=1 steam), but that does not work on my system -- Steam will not start at all.

Based on this example I tried running both the game and SteamVR with env DRI_PRIME=pci-0000_03_00_0 %command% in their launch options, and that made it work. I have a clear picture now.

Bbadjware 2024-06-11 github

Replying to https://github.com/ValveSoftware/SteamVR-for-Linux/issues/640#issuecomment-2148320102

This comment inspired me to check something.

I went into the BIOS and set "Initial Graphic Adapter" to "PEG". It was set on "IGD". This has fixed the problem on my system without resorting to environment variable.

It seems that this issue may have something to do with the integrated graphic adapter.

Specs:
Mobo: MSI PRO B660M-A
CPU: Intel i7-12700k
GPU: AMD Radeon RX 7800XT

MmaterusPL 2025-12-22 github

I'm having this problem when iGPU is my primary card in stationary PC.
Ryzen 7900X iGPU + Radeon 7900 XTX.

It happens when displays are connected to iGPU but trying to render on dGPU. When I started steamvr on iGPU it rendered fine but performance was horrible.
When connected displays to dGPU and set it as primary card it also render fine, but due to my virtual machine configuration I prefer to have displays connected to iGPU.

Edit: Starting Steam with DRI_PRIME seems to fix it, it is not ideal since steam doesnt work with DRI_PRIME when desktop session is using different gpu as primary.

RRSDNTWK 2026-02-23 github

We commented on it here: https://github.com/alvr-org/ALVR/issues/2373 and despite out testing it's still an issue.

We are using the Framework laptop 16 with the 780M iGPU on the Ryzen 9 7940HS with the RX 7700S dGPU Module.

This bug affects multiple distros including Debian, Ubuntu, Arch Linux and Fedora using both X11 and Wayland compositors.

Our iGPU is necessary as it acts as a passthrough for the dGPU and disabling it disables the display output for the entire system.

PPacketdancer 2026-04-06 github

@materusPL - Just to double-check, are you using a wireless HMD (e.g. vrlink) or are you using a wired one?

MmaterusPL 2026-04-07 github

@Packetdancer I had this problem on both wired (Index) and wireless (Quest 2).
My index stopped working so can't check if DRI_PRIME helps for that

PPacketdancer 2026-04-07 github

Reason I ask is that they'd have two similar but not identical causes, so I wanted to know which I should check (or if it was both).

For the wireless case, I can say that I've got a fix in the pipeline for a future build, so that it will be possible to use the dGPU for wireless HMD even when your physical displays are plugged into the iGPU as primary. (In fact, it will try to do that by default with that change.) Not sure when it'll land in the real builds, though.