Consolatis

When `wlr-randr` shows a scale factor of `1`, does the game then provide the correct resolution?

While technically correct, this is kind of a wlroots / xwayland and thus labwc issue. > If I understand the settings correctly you are describing in the manual, the wlr-randr...

rootful xwayland is supported by labwc (and should be the same for any other wayland compositor as its basically just a regular wayland client from what I remember): ``` Xwayland...

I do use nano as my main code editor for C and some Python. It uses simple regex based highlighting and that works surprisingly well. So a pure regex based...

> When coming back from resume, scale is 1.0. This is how labwc sees it and sets surfaces accordingly. _Suddenly_, just at this time, the scale is set to 2.0...

This seems to be the relevant part: ``` $ egrep '(discarded|enter|global_remove|set_buffer_scale|#41)' ~/Downloads/debug_bad.log [3190089.005] {Default Queue} -> wl_surface#34.set_buffer_scale(2) [3190089.025] {Default Queue} -> wl_surface#34.frame(new id wl_callback#41) [3190092.150] {Default Queue} wl_surface#34.enter(wl_output#20) [3190092.384] {Default...

Didn't check further but [this](https://github.com/GNOME/gtk/blob/gtk-3-24/gdk/wayland/gdkscreen-wayland.c#L1858) at least looks like an event is emitted (which then likely has one of its handlers indirectly dispatch more wayland events, causing the incoming scale...

Any difference when using the master branch? Background: #2812 has been merged which enables another scale event so GTK 3 might not be required anymore to rely on the broken...

Well, it was worth a try. Thanks for testing.

In general I like this policy, and I am completely fine with adding it to labwc. Personally I'd also be open to use this as a default when everything is...