00:08 <dviola> looks like it never worked pre qt v6.0.0

00:12 <dviola> yes, so backporting this commit essentially fixes the issue: https://invent.kde.org/qt/qt/qtbase/-/commit/7238123521708ec94edd816d5b668978c002b17a

00:31 <dviola> just dropped a comment on the bug report: https://bugreports.qt.io/browse/QTBUG-108602

00:31 <dviola> bah, keepassxc locked the conversation

00:34 <dwfreed> dviola: your comment is on that bug report to my eyes

00:43 <dviola> heh

06:33 <dviola> so apparently the change I made is wrong

06:33 <dviola> "It's removing physical dpi fallback (breaking change)"

06:34 <dviola> ilya-fedin[M] │ A real fix (without behavior change) would likely be something different

06:34 <dviola> ilya-fedin[M] │ it might as well indicate there's something wrong with sway's xwayland integration and xwayland reporting insane dpi when you disconnect the screen

06:34 <dviola> #kde-devel

06:34 <dviola> how can I rule out that ("it might as well indicate there's something wrong with sway's xwayland integration and xwayland reporting insane dpi when you disconnect the screen")

06:36 <dviola> I wonder why Qt6 decided to go that way then

08:13 <dviola> https://gitlab.freedesktop.org/xorg/xserver/-/commit/b0413b6e99c6b5fbc04229ce64ddf1f41b08e63e

11:13 <zzxyb[m]> How to know from the wayland protocol whether wl_pointer is a mouse or a touchpad device?

11:39 <vyivel> zzxyb[m]: you can't, nor is it possible: a wl_pointer can be controlled by multiple physical devices at the same time

21:06 <wlb> wayland Issue #510 opened by () Apps have input sleep after 10 seconds https://gitlab.freedesktop.org/wayland/wayland/-/issues/510

21:08 <bluetail> thats a weird one

21:41 <wlb> wayland Issue #510 closed \o/ (Apps have input sleep after 10 seconds https://gitlab.freedesktop.org/wayland/wayland/-/issues/510)

21:43 <wlb> wayland-protocols Merge request !367 opened by () Amend ext-idle-notify-protocol to work properly with apps for mitigating RSI https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/367

22:13 <dviola> https://github.com/keepassxreboot/keepassxc/issues/8758#issuecomment-2526387774

22:13 <dviola> some KDE people think this is a Xwayland bug

22:13 <dviola> how can I rule that out?

22:14 <dviola> return QDpi(96, 96); makes it work, return QDpi(std::max(virtualDesktopPhysicalDPi.first, 96.0), produces the missing font issue

22:14 <dviola> I'm not sure what that `virtualDesktopPhysicalDPi.first` is returning

22:15 <dviola> but it seems to be only a problem with QT_QPA_PLATFORM=xcb and not with QT_QPA_PLATFORM=wayland

23:20 <dviola> https://gitlab.freedesktop.org/xorg/xserver/-/commit/b0413b6e99c6b5fbc04229ce64ddf1f41b08e63e

23:23 <dviola> "However, if the Wayland outputs get reconfigured, or new outputs added, or existing outputs removed, Xwayland will recompute and update the physical size of the screen, leading to an unexpected change of DPI."

23:24 <dviola> yeah this is what is happening, but looks like xwayland sets it to 96 there to alleviate the problem

23:26 <dviola> this is what is happening I think*

23:55 <znarf> Im currently implementing my own wayland client from scratch and Im having trouble sending an fd to the server for shm_create_pool. I can send it via `sendmsg` and it does arrive (I've fstat'ed it on the server side as a sanity check, which worked). However the server sends me this `-> wl_display#1.error(wl_display#1, 1, "invalid arguments for wl_shm#4.create_pool")` and logs this internally: `file descriptor expected, object (4), me

23:56 <znarf> what completely puzzles me is that it logged this right before: `wl_shm#4.create_pool(new id wl_shm_pool#9, fd 84, 16384)` (thats a working fd for that fstat gives the correct size) so the fd does very much seem to arrived and been associated with the correct request