kyak
kyak
Debug log for reproducer app made on the working 0.8.3-66-gb3e80f3a (all crisp): [debug.log](https://github.com/user-attachments/files/20510349/debug.log)
Debug log for reproducer app made on the "bad" labwc. This time with running `wlr-randr --output eDP-1 --scale 1; wlr-randr --output eDP-1 --scale 2` after resume to make it crisp:...
Debug log for reproducer app made on the "bad" labwc. This time with running `wlr-randr --output eDP-1 --off && wlr-randr --output eDP-1 --on` (not doing suspend/resume at all). kanshi is...
Debug log of "bad" labwc, just the suspend/resume cycle: [labwc_debug.txt](https://github.com/user-attachments/files/20511204/labwc_debug.txt)
As suggested by @Consolatis , i patched gtk3 like this: ``` diff --git a/gdk/wayland/gdkscreen-wayland.c b/gdk/wayland/gdkscreen-wayland.c index 79bd221055..f2db75f9f3 100644 --- a/gdk/wayland/gdkscreen-wayland.c +++ b/gdk/wayland/gdkscreen-wayland.c @@ -1855,8 +1855,8 @@ _gdk_wayland_screen_add_output (GdkScreen *screen, monitor->version...
There are side effects of this gtk3 patch. For example, when alt-tabbing between alacritty and firefox, firefox window glitches (it goes from scale 1 to scale 2 quite visibly). Both...
> Any difference when using the master branch? Background: [#2812](https://github.com/labwc/labwc/pull/2812) has been merged which enables another scale event so GTK 3 might not be required anymore to rely on the...
Are there any workarounds for that?
> I think the obvious solution would be to have some kind of scroll box. Why? The behaviour in most (all?) panels is to shrink window buttons to fit.