[BUG] VRInitError_IPC_CompositorConnectFailed

[ogrady]

Describe the bug
Connecting to SteamVR from Quest 3 crashes SteamVR on Linux.
Appears to be related to/ same issue as #623

To Reproduce
Steps to reproduce the behavior:

1. Open SteamVR on Linux PC
2. Open Steam Link on Quest 3
3. Select Linux PC to connect to
4. Steam briefly launches (Steam logo with spinning blue loading indicator), then crashes on PC with:

SteamVR failed initialization with error code VRInitError_IPC_CompositorConnectFailed: "Shared IPC Compositor Connect Failed (306)"

Please verify SteamVR is properly installed and try again.

Expected behavior
Quest 3 should connect to Steam running on Linux and stream games from there.

System Information (please complete the following information):

• Steam client version (build number or date):

Steam Beta Branch:  Stable Client
Steam Version:  1763795278
Steam Client Build Date:  Sat, Nov 22 8:00 AM UTC -08:00
Steam Web Build Date:  Sat, Nov 22 7:35 AM UTC -08:00
Steam API Version:  SteamClient023

• SteamVR version: 2.14.3 (beta)
• Distribution: Nobara
• Steam runtime diagnostics: https://gist.github.com/ogrady/de2129e7bc1cd6402c2c985ac2a20c61
• Steam and SteamVR logs: steam-logs.tar.gz
• Minidumps: steam-minidumps.tar.gz

Gist containing SteamVR info

Additional context
I am not even entirely sure if this is a singular problem, as I have encountered multiple other issues along the way:

• SteamVR connecting fine, being able to launch Steam Home (implying that generally streaming the video feed works), then successfully starting a game, but crashing with "Host is connected, but not streaming video" while I can hear the game audio
• SteamVR just crashing with "Oh no! SteamVR has encountered an unexpected problem. (-201)" without further explanation
• SteamVR just timing out upon connect

But the the most prevalent seems to be error 306.

I also found some threads on Reddit describing this error when too many displays were connected (more than four, including the HMD).
In my case, I only have a single monitor connected via HDMI, plus the HMD. I also tried no monitor at all, with just a DP dongle attached. Same outcome.

[ogrady]

Hi @anuxagfr, thanks for chiming in. Not very keen to download random .zip files from strangers, sorry.

[pduggusa]

⚠️ SECURITY ALERT

User @anuxagfr is part of a coordinated mass supply chain attack.

DO NOT DOWNLOAD any .zip files from this user.

• 13 repositories attacked in 19 minutes
• Targets: Microsoft VSCode, GrapheneOS, Valve SteamVR, IBM Terraform
• Pattern: 104-day sleeper account activated for malware delivery
• Reported to GitHub Security

—DugganUSA Threat Intelligence

[DieEneSchrodinger]

I am having the same issue using a Quest 2

To Reproduce
The same as ogrady

Expected Behaviour
The same as ogrady

System Information (please complete the following information):

• Steam client version: 1763795278
• SteamVR version: 2.14.3 (beta and stable0
• Distribution: Zorin OS 18
• Steam runtime diagnostics: runtime diagnostics gist
• Steam and SteamVR logs: steam-logs.tar.gz
• Minidumps: steam-minidumps.tar.gz

I at first also had an isssue with setting the OpenXR runtime, though this was able to be fixed by using the vrmonitor.sh file on the command line and editing the vrenv.sh file to use exec "./$@" rather than exec "$@".

[Reelix]

This has been a sporadic issue across multiple headsets (Not only Oculus / Meta products) and dozens of SteamVR versions since around 2017 (And - Whilst affecting Linux users - Is not specific TO Linux).

Whilst the issue is commonly attributed to dual-screen setups, it also frequently appears for users with single monitors.