Setting a custom mode breaks with sway
I have overclocked my monitors to run at 75 Hz instead of their standard 60 Hz. (relevant config)
I am running Debian Sid, and I'm tracking both wlroots and sway from master. Some time ago I started having weird issues with my monitors:
- The wallpaper (using swaybg) did not load for both of my external monitors (they are both connected to an external GPU via thunderbolt 3)
- Some applications - for example Firefox - seemed to have no anti-aliasing enabled and thus text/icons were very blocky.
- Waybar only loaded on my laptop monitor, not the external ones (the laptop monitor is not using a custom mode)
- If I disabled my laptop display by closing the lid, I was not able to launch any wayland applications, as sway claimed there were no global monitor objects.
I quickly reverted to a known good commit for both sway and wlroots and carried on.
Today I bisected the issue to this commit: e85c7905. However, the symptom is a bit different: with this commit sway does not launch at all. Some commit after it has changed the crash into the current symptoms. I can bisect that part further if it helps.
Both that commit and the current wlroots master start working if I remove the custom mode from my configuration - but that of course drops me back to 60 Hz...
Setting the custom mode after sway has launched results in the exact same behavior - at least with the current master.