search

ValveSoftware / SteamVR-for-Linux

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

[BUG] System crash and logs off when opening non-steam VR game #730

Closed Murilovsky closed 3 months ago

Murilovsky commented 3 months ago

Describe the bug Trying to play a non-steam VR game in SteamVR freezes the screen in both HMD and Monitor immediately. The computer user session ends after some time. Happens on Native and Proton Games

To Reproduce Steps to reproduce the behavior:

  1. Download any VR game from anywhere other then Steam (Used OpenSaber as an example)
  2. Add it to the game to the library as a Non-Steam game
  3. Check the "Include on VR Library" toggle in game's properties
  4. Run the added game

Expected behavior The game opens and shows on screen, or maybe crash but without hanging the system/session

System Information:

Additional context Using ALVR to stream game from PC to Oculus Quest 2

kisak-valve commented 3 months ago

Hello @Murilovsky, for reference, your first crash_ minidump is a SIGABRT in libc.so.6 coming from radeonsi_drvvideo.so and your second crash minidump is a SIGABRT in libc.so.6 coming from vrcompositor.real.

From your console-linux.txt log:

>>> Starting desktop stream
WARNING: Desktop capture unavailable, try running Steam with -pipewire
amdgpu: The CS has cancelled because the context is lost. This context is innocent.
crash_20240811145111_2.dmp[17881]: Uploading dump (out-of-process)
/tmp/dumps/crash_20240811145111_2.dmp
crash_20240811145111_2.dmp[17881]: Finished uploading minidump (out-of-process): success = yes
crash_20240811145111_2.dmp[17881]: response: CrashID=bp-5ef014ac-8088-4600-8c68-10eb72240811
crash_20240811145111_2.dmp[17881]: file ''/tmp/dumps/crash_20240811145111_2.dmp'', upload yes: ''CrashID=bp-5ef014ac-8088-4600-8c68-10eb72240811''
X connection to :0 broken (explicit kill or server shutdown).

It hints that Steam Remote Play was starting up vaapi encoding, there was a video driver issue, and X got kicked out from underneath everything. This issue should be reported to your video driver vendor.

Murilovsky commented 3 months ago

Okay. Thanks for clarifying!