Switching between Sway and Cage VTYs behaves weird

[puckipedia]

When I have sway open in tty1 and cage in tty2, switching between them behaves weirdly:

• Switching from sway to cage directly causes a specific output to not refresh.
• If I switch from sway to a tty with login prompt, and then to cage, it refreshes properly.
• If the output refreshes, it happens at the base refresh rate of this screen (48Hz),, with up to 144Hz VRR) even if VRR is *disabled* (but enabled under the sway session)

While the output is not refreshing, wlr-randr is also unable to disable the output either.

[emersion]

Please attach debug logs.

[puckipedia]

Attached the debug logs for the VT switching.

I'm unsure the VRR thing was actually an issue and not an artifact of the application i was running as i was unable to replicate what the issue was.
cage.log

[emersion]

Hm. Can you try reproducing with latest wlroots with #281?

00:00:06.153 [INFO] [backend/drm/drm.c:586] connector HDMI-A-1: Modesetting with 2560x1440 @ 143.933 Hz
00:00:06.153 [ERROR] [backend/drm/atomic.c:71] connector HDMI-A-1: Atomic commit failed: Invalid argument
00:00:06.153 [DEBUG] [backend/drm/atomic.c:75] (Atomic commit flags: PAGE_FLIP_EVENT | ATOMIC_ALLOW_MODESET)
00:00:06.153 [ERROR] [backend/drm/backend.c:123] connector HDMI-A-1: Failed to restore state after VT switch

[puckipedia]

Works when compiling against commit ddfec31b4c2a6fe289f1966a49403b802d85314a (just before removing wlr_idle). However, the X position of the secondary monitor is now ignored. wlr-randr still shows it at the right position, and the mouse cursor still behaves as if the output layout were rendered correctly.

And cage segfaults on exit.