Open dsalt opened 4 years ago
With my testing patch in place (see the X bug report, linked above), shutting SteamVR down normally works fine; but sending SIGHUP
will cause it to terminate quickly, which is likely to cause X not to complete the lease clean-up, such that the lease is still active but not assigned to any running client..
I can confirm that I have the same symptoms on Xwayland as that bug report, where unplugging it is required between every launch.
It happens randomly for me. Sometimes on first launch, sometimes on subsequent launches.
Ubuntu 22.10 KDE desktop and session manager (vanilla) SteamVR beta (as of Jan 04 2022)
This tends to occur on the second and subsequent runs of SteamVR in any given X session. I have never observed it on first run (though it's technically possible, it requires something else to have made use of the HMD).
The bug is, so far as I can tell, actually an X bug,: it looks like a race between lease termination and cleanup due to X client termination. (Bug report is here.) From reading xserver source, it seems to me that a workaround is possible by having vrcompositor wait for a short time for an RRLeaseNotifyEvent message from the X server before exiting.