SteamVR-for-Linux icon indicating copy to clipboard operation
SteamVR-for-Linux copied to clipboard

[BUG] Issue Title

Open Oman395 opened this issue 2 years ago • 3 comments

The title pretty much says it all. When I close steamvr, it completely hangs my OS, and it takes a REISUB to fix (hung to the extent that capslock doesn't even light up when I press it...). This is relatively consistent, but for some reason when I close with steam it closes without issue.

Steps to reproduce the behavior:

  1. Open SteamVR
  2. Close SteamVR through pretty much any means (although closing through steam sometimes doesn't crash it, so that's something...?)

System Information:

  • Distribution: Arch
  • SteamVR version: 1.24.7
  • Steam client version: Dec 15, 2022
  • Opted into Steam client beta?: No
  • Graphics driver version: 525.60.11
  • Gist for SteamVR System Information: https://gist.github.com/Oman395/c779fcaafe89b5bf5c2b7b85770e0a9b

Screenshots image

Additional context I've been seeing some weird logs in dmesg that pretty much say that there are issues with the literal main USB bus, maybe related to #312 and could potentially be something weird with the IO?

Oman395 avatar Dec 24 '22 00:12 Oman395

Hello @Oman395, this issue should also be mentioned to your video driver vendor. Please adjust the title of this issue report.

kisak-valve avatar Dec 24 '22 00:12 kisak-valve

I saw this same behavior. I nuked the ~/.steam directory and it is no longer crashing. This was with the latest Nvidia driver nvidia-glG06-32bit-525.60.11 In any event, I did manage to get a crash log by remote login, which rarely worked. crash.txt

aaronw2 avatar Dec 25 '22 12:12 aaronw2

This was affecting me recently - Every time I exited SteamVR no matter how I did it it would take my whole system out and require a REISUB reboot.

First I tried deleting the config and logs folders in ~/.steam/steam and I had partial success. SteamVR would hang on exit but no longer took my system with it.

Then I removed ~/.steam an re-installed Steam. After re-launching all seems to be well again. Ultimately not sure what caused it but thank you @aaronw2 your solution worked for me also.

Just sharing in case people come across this in the future.

vsTerminus avatar Jul 14 '24 06:07 vsTerminus