`DrmDevice::new` with disable_connectors = true causes vrr_capable property to get stuck at 0

[YaLTeR]

`DrmDevice::new` with disable_connectors = true causes vrr_capable property to get stuck at 0

[YaLTeR]

Just noticed that sleep-resume while niri is running switches the vrr_capable property to 1. And a subsequent VT switch back and forth brings the property back to 0 (I guess due to the call to reset_state()).

[YaLTeR]

It's also possible to switch VRR on in sway and switch VT back to niri, which results in a combination of vrr_capable = 0 and VRR_ENABLED = 1. Unfortunately, on this laptop screen it doesn't seem to do anything (and neither it does in sway).

[YaLTeR]

Some new developments (Fedora 40, kernel-6.8.4-300, mesa-dri-drivers-24.0.4-1):

• when vrr_capable is bugged to 0, setting VRR_ENABLED on that connector succeeds but does nothing (same as setting VRR_ENABLED on a connector that is normally not vrr_capable)
• unplugging an unrelated monitor causes vrr_capable to unbug and become 1, then setting VRR_ENABLED will work and enable VRR
• when vrr_capable is bugged to 0 and VRR_ENABLED is at 1 left over from another TTY, setting VRR_ENABLED to 0 does not succeed. It remains at 1 which sometimes does nothing and sometimes enables VRR on a different monitor? Not sure.