protonscr

[BUG] SteamVR Doesn't Properly Close

steamvrclosed bug
ValveSoftware/SteamVR-for-Linux#892 · opened 2026-05-02 by Meolsei · updated 2026-05-12 · 3 comments · github
MMeolsei 2026-05-02 github

Describe the bug
After quitting SteamVR from the VR menu, Steam continues to show a 'Stop' button which is unresponsive and does not kill the remaining processes. The only resolution I've found is manually sending a SIGKILL to the remaining proecsses, after which Steam finally updates.

To Reproduce
Steps to reproduce the behavior:

  1. On the Meta Quest 2, launch SteamVR using Steam Link
  2. Quit SteamVR from the VR menu
  3. Observe the Steam UI stuck on the unresponsive 'Stop' button.

Expected behavior
SteamVR should correctly shut down, and Steam's UI should return to the normal 'Play' button state.

System Information (please complete the following information):

Screenshots
N/A

Additional context

  • Headset: Meta Quest 2 (Via Steam Link)
  • Window Manager: i3 over X11
  • CPU: AMD Ryzen 5 3600
  • GPU: AMD Radeon RX 5500 XT (AMDGPU)
  • Audio: PipeWire with WirePlumber

I've only had the issue recently, but the workaround I've resorted to is by sending a SIGKILL to the following processes:

pkill -9 vrserver
pkill -9 vrcompositor
pkill -9 vrdashboard
pkill -9 vrmonitor
pkill -9 vrwebhelper

journalctl shows zero SteamVR related output at any point.

PPacketdancer 2026-05-11 github

There's a known edge case where vrserver is not exiting cleanly, but it's proving annoyingly hard to track down (mostly because it won't happen in a debug environment).

So: known, already being looked at. :)

MMeolsei 2026-05-11 github

There's a known edge case where vrserver is not exiting cleanly, but it's proving annoyingly hard to track down (mostly because it won't happen in a debug environment).

So: known, already being looked at. :)

Ah, thanks for letting me know then! Hope it can be resolved quickly, this one seems strange.

PPacketdancer 2026-05-12 github

Yep. You may want to go subscribe to on #876 to keep an eye on when there's a fix, since that's the issue tracking it. :)

Nothing extracted yet.