Stuck(?) in VT handling when there is an existing drm master
Observe the following scenario:
- Open VT A, start weston
- Open VT B, start an app which gets drm master and never drops it - for example kmscube
- Toggle to weston, observe app B (kmscube) - that's expected
- Weston is stuck(?) in the VT handler - VT switch fails, cannot even toggle to VT B to close app
- Kill or otherwise close app B
- Weston is still stuck(?) in the VT handler - VT switch fails
- Kill weston to get back out
Notes:
- X does the opposite bad thing - it crashes immediately Yet, session managers such as sddm, will repeatedly spawn X. Which will fail until app A is stopped.
- This is with the logind backend, yet the direct drmSet/DropMaster is also broken as mentioned in #161
What's expected:
- being able to VT out of A
- weston should recover after app B is closed