[swaywm] [GDK_BACKEND=wayland] incorrect maximum window geometry on secondary monitors
So, on my second monitor (second in that it's listed second in swaymsg -t get_outputs
and in xrandr
), most libadwaita-based applications seem to be shorter than they should be. This is especially ugly when using the tabbed mode of swaywm.
On my secondary monitor:
On my primary monitor:
In fact, I checked in GNU IMP and the incorrect short window height is exactly 1080 px—the height of my primary monitor. It would seem that somewhere, there is some code that is limiting the size of the window to fit within the bounds of the monitor, but does not account for secondary monitors having different sizes. Or maybe the limit is to the smallest monitor, not necessarily the primary one.
I did some more testing, and I can say that on sway with GDK_BACKEND=x11
, or on i3, each of nautilus, gnome-text-editor, gnome-calendar, and gnome-clocks all have the correct geometry, but do not respect GTK_THEME
.
But as you can see in the screenshot, on sway with GDK_BACKEND=wayland
, on my second monitor,
- nautilus, gnome-text-editor, and gnome-calendar all respect
GTK_THEME
but do not have correct geometry; - gnome-clocks somehow does not respect
GTK_THEME
but has the correct geometry.
Sometimes I can get the geometry to correct itself if I fullscreen the window and then un-fullscreen it, but then after a few seconds it will snap back to being too small.
Also, I tried com.usebottles.bottles
(Flatpak) and it behaves like nautilus et al. except it obviously never respects GTK_THEME
.
This issue was previously reported as https://github.com/swaywm/sway/issues/7000 but a developer suspected it was a libadwaita bug since it doesn't happen with GDK_BACKEND=x11
.
Please let me know what I can do to help solve this! It's very annoying as my "secondary" monitor is actually the one I use most of the time.