-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Room setup won't start #458
Comments
Hello @davegorst, not that it directly helps, but the SIGPWR backtrace is a red herring and expected. If you want to use GDB to troubleshoot mono, then you need to ignore some signals with |
Interesting. Thanks. |
OK - a bit further now : #1 0x00007fff6c49174d in CSharedSemaphoreLinux::ImportVulkanSemaphore(VkDevice_T*, unsigned long) () Seems to be dying while starting the compositor : |
Have you tried rolling back to v1.14 in the betas tab to see if it'll let you complete room setup there? |
Yeah - I rolled forward to the beta to see if it fixed the issue. I'm going to try a full reinstall and see if that helps once I've finished backing everything up. |
Just a blind guess here. Ubuntu 21.04 ships with Wayland as default which doesn't work with SteamVR yet. Was in a similar situation last week when I installed Arch, devices light up in SteamVR, but they're not detected in Room Setup, and SteamVR throws an error 307 IIRC. Fixed by switching to X11 instead of Wayland at login. |
I also can't start Steam VR Room setup. Running KDE x11 on Arch.
|
Switching back to the 20.04 LTS release seems to have fixed the issue. Hopefully it'll be fixed soon for 21.04+. |
For the record, same issue with EndeavourOS rolling. X11 GNOME 40.4 with RX 5700 XT amdgpu driver, all my other XR stuff works fine including Monado. So that narrows the issue down a bit more. |
The issue was totally resolved by switching from amdvlk to vulkan-radeon. Looks like AMD's vulkan driver is out of date but Mesa's isn't! |
Same issue on NixOS 22.05: NixOS/nixpkgs#177197 |
Likely the NixOS issue is entirely due to how the NixOS system is designed and more similar to the issue that SteamVR has in flatpak right now. |
@HadetTheUndying i have actually used that workaround to get rid of the error message, but the room setup does still not start. |
I'm wondering if NixOS still has issues with udev. I know it was an issue before with controllers |
I don't think so. The option
does install udev rules. The Valve Index and Controllers and PS4 Controller works. |
I am also having this issue on Ubuntu 22.04 LTS. |
Alright, so after much fiddling, it turns out that rolling back to Ubuntu 20.04 LTS was not the best solution.
These are the steps that I did to get it to work. I don't know if they will work for you, I also don't know why you have to leave the linux beta to be able to play games. If you find yourself here, keep trying things until something works, and then share what worked for you. |
Room setup is working fine for me on NixOS 22.11 with SteamVR 1.24.6. |
Your system information
Please describe your issue in as much detail as possible:
Moved to another machine with a new nVidia GPU (3060). System appears to be working (headset display working and showing bases and controllers), but attempting to start room setup opens inital window then immediately fails.
gdb reporting an issue with libmono.so when starting from command line :
Thread 4 "steamvr_room_se" received signal SIGPWR, Power fail/restart.
[Switching to Thread 0x7ffff1ba3640 (LWP 21426)]
__futex_abstimed_wait_common64 (cancel=true, private=, abstime=0x0, clockid=0, expected=0, futex_word=0x7ffff281c070) at ../sysdeps/nptl/futex-internal.c:74
74 ../sysdeps/nptl/futex-internal.c: No such file or directory.
(gdb) bt
#0 __futex_abstimed_wait_common64 (cancel=true, private=, abstime=0x0, clockid=0, expected=0, futex_word=0x7ffff281c070) at ../sysdeps/nptl/futex-internal.c:74
#1 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7ffff281c070, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=) at ../sysdeps/nptl/futex-internal.c:123
#2 0x00007ffff7f7840f in do_futex_wait (sem=sem@entry=0x7ffff281c070, abstime=0x0, clockid=0) at sem_waitcommon.c:112
#3 0x00007ffff7f784a8 in __new_sem_wait_slow64 (sem=0x7ffff281c070, abstime=0x0, clockid=0) at sem_waitcommon.c:184
#4 0x00007ffff24fb903 in mono_sem_wait () at /home/dgorst/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/x86_64/libmono.so
#5 0x00007ffff2465f89 in () at /home/dgorst/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/x86_64/libmono.so
#6 0x00007ffff24cdc6c in () at /home/dgorst/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/x86_64/libmono.so
#7 0x00007ffff24f381b in () at /home/dgorst/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/x86_64/libmono.so
#8 0x00007ffff2514366 in () at /home/dgorst/.local/share/Steam/steamapps/common/SteamVR/tools/steamvr_room_setup/linux64/steamvr_room_setup_Data/Mono/x86_64/libmono.so
#9 0x00007ffff7f6f450 in start_thread (arg=0x7ffff1ba3640) at pthread_create.c:473
#10 0x00007ffff7b02d53 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Steps for reproducing this issue:
The text was updated successfully, but these errors were encountered: