You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When launching SteamVR, I receive a prompt to run room setup. Room setup then appears to auto-launch in a window which immediately crashes. I then can't get it to open in any other way. Attempting to launch it from the SteamVR dock produces no noticeable results, attempting to launch it through the regular Steam window yields this:
Running the executable outside of steam produces these results ( from terminal):
Set current directory to /home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64
Found path: /home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup
Mono path[0] = '/home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Managed'
Mono path[1] = '/home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono'
Mono config path = '/home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/etc'
Preloaded 'libopenvr_api.so'
Unable to preload the following plugins:
ScreenSelector.so
Aborted (core dumped)
This is when run from the beta release, it seemed to preload ScreenSelector.so fine when using Stable for both SteamVR and Steam but crashed similarly each time.
To Reproduce
Steps to reproduce the behavior:
Launch Steam VR from Steam
(Optionally) Attempt to launch it again. Expected behavior
Room setup launches as normal.
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
Steam client version (build number or date): December 20th Beta (Also occurs in latest stable release)
SteamVR version: beta 2.9.4 (same behavior in 2.8.8
Describe the bug
When launching SteamVR, I receive a prompt to run room setup. Room setup then appears to auto-launch in a window which immediately crashes. I then can't get it to open in any other way. Attempting to launch it from the SteamVR dock produces no noticeable results, attempting to launch it through the regular Steam window yields this:
Running the executable outside of steam produces these results ( from terminal):
Set current directory to /home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64
Found path: /home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup
Mono path[0] = '/home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Managed'
Mono path[1] = '/home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono'
Mono config path = '/home/decker/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/etc'
Preloaded 'libopenvr_api.so'
Unable to preload the following plugins:
ScreenSelector.so
Aborted (core dumped)
This is when run from the beta release, it seemed to preload ScreenSelector.so fine when using Stable for both SteamVR and Steam but crashed similarly each time.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Room setup launches as normal.
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
Steam client version (build number or date): December 20th Beta (Also occurs in latest stable release)
SteamVR version: beta 2.9.4 (same behavior in 2.8.8
Distribution (e.g. Ubuntu): Arch Linux
Steam runtime diagnostics:"LD_* scout runtime" information:
Steam Runtime Diagnostics.txt
Steam and SteamVR logs:
steam-logs.tar.gz
Minidumps: [run the following command:
tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps
]steam-minidumps.tar.gz
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Attempted workarounds mentioned in #694 without success.
The text was updated successfully, but these errors were encountered: