03:26 <wlb> wayland-protocols Merge request !416 opened by Peter Hutterer (whot) tablet: fix all comment-references to the zwp_tablet elements https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/416

03:38 <wlb> wayland Merge request !434 closed (src: Add feature of printing PID, ClientName and Timestamp)

06:18 <wlb> wayland Merge request !478 opened by zhenyan huang (hzy) logging: Add PID, ClientName for debug logging https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/478

08:13 <wlb> wayland Merge request !438 closed (Fix build of C++ code with clang >= 16 and -Wundef)

10:50 <bluetail> Hello!

10:53 <bluetail> I am having an issue on a wlroots based tiling manager called sway. in xwayland, message toasts of different types that are not focusable can steal focus! Such as JDownloaders message toast or filebot's message toast. For filebot, I did even look with xprop into it. https://0x0.st/8E8F.txt

10:54 <vyivel> bluetail: that's a sway bug

10:54 <bluetail> OK. I'll ask in sway.

12:06 <wlb> weston/main: Marius Vlad * backend-drm: Use a local variable to store output frame rate data https://gitlab.freedesktop.org/wayland/weston/commit/a4494f2ea38c libweston/backend-drm/kms.c

12:06 <wlb> weston Merge request !1775 merged \o/ (backend-drm: Use a local variable to store output frame rate data https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1775)

12:12 <wlb> wayland-protocols Merge request !417 opened by Pekka Paalanen (pq) staging/color-management: recommend gamma22 instead of srgb https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/417

15:15 <aelius> How does one remotely wake a monitor on wayland? I'm having an issue where my remoting software (sunshine) using kms capture "can't find a monitor" if it's sleeping. Annoyingly, I have an hdmi dummy plug, but I wouldn't know how to disable idle timeout for the plug, but not the real display

15:28 <bluetail> aelius just use ddcutil

15:30 <bluetail> ssh user@remote.local 'ddcutil setvcp 60 0x11 --display 1' or whatever else. Just switches to output HDMI. U could also go from HDMI to DP and back. But in any case. If the monitor speaks ddc - which most do, it will definitely wake your little sleeper

15:30 <bluetail> I think 0xf was for DP

15:34 <aelius> will investigate, thanks

15:35 <aelius> hoping sunshine execing that on connect will work too

18:42 <Guest17913> Question, if I want to display a window to know the size, I need to know the dpi/scaling of the monitor I going to be shown on.. Is it possible to get this *before* I display a frame? now I know it after the first buffer is shows. I want to avoid resizing after the first frame, as this triggers an animation.

18:57 <zamundaaa[m]> Guest17913: dpi and scale are very different things. Which one do you want?

18:59 <zamundaaa[m]> If you want the scale, the fractional scale protocol gives it to you. You should get it together with the other configure events for the window, before it's shown

19:00 <kennylevinsen> note that the position of a window is not decided till *after* you submit your content, as e.g. geometry and other details might affect placement decisions and which outputs you overlap with - but yes, for scale, you can get an early hint of what the Wayland server would like you to use

19:02 <Guest17913> Its an overlaying window and what happens now is I render one frame. then I find out the dpi. I update the fonts, recalculate all the sizes and rerender everything at the right size for the next frames.. but that gives an nice little resize animation effect in hyprland. so I wondered if I could get this info before the first frame buffered.

19:02 <Guest17913> one monitor is fine, multi monitor with different dpi's its an issue

19:35 <kennylevinsen> Guest17913: normal clients should never concern themselves with dpi, only scale. rendering at different scales does not change sizing.

19:36 <kennylevinsen> only very special clients that have a specific need to render a physically-accurate representation should ever think about dpi

19:42 <Guest17913> yeah, that is what I allow clients to do.. specify an actual width.

19:43 <Guest17913> have some figuring out on X11 to make sure that the window would show exactly the same size on any monitor it was shown on

19:43 <Guest17913> trying to keep that functionality