00:04 exkc: whot1: i think it is both a touch pad and touch screen drvier
00:05 exkc: maybe also stylus?
00:15 soreau: exkc: not to be assumed
00:16 exkc: alr
00:51 exkc: sry
00:52 karl3fox: That's legit soreau, ill go fixate my ADHD brain on something else for a bit
01:45 karenw: Is it possible to force libdecor to select a different backend?
01:45 karenw: s/backend/plugin
01:47 riteo: karenw: I have no idea either but a quick workaround I use is copying the plugin I need to a random dir and set the libdecor plugin dir env var to point to it
01:47 riteo: one sec I'll look it up cause I don't remember it by heart
01:48 riteo: `LIBDECOR_PLUGIN_DIR`
01:48 riteo: also a quick `git grep getenv` returns no envar that might do that, so I'm afraid it's not possible to force a specific plugin
01:49 karenw: I guess I can just spin up `mutter --nested` and set WAYLAND_DISPLAY to e.g. force gtk backend
01:49 karenw: I'll give the LIBDECOR PLUGIN DIR a go, thanks.
02:03 riteo: yw
05:52 vyivel: hm w-p 1.38 isn't on https://wayland.freedesktop.org/releases.html
11:01 emersion: jadahl: ^
18:19 dviola: hi, the issue I mentioned the other day with fonts disappearing after my monitor going off/on with bitcoin-qt also happens with other qt5 apps (keepassxc), so it's probably something else other than the app itself, how can I rule out this being a qt5 issue or a driver/xwayland issue?
18:31 kennylevinsen: dviola: Drivers and Wayland are not involved in fonts. Wayland deals with stuff that has finished drawing
18:33 dviola: makes sense
18:33 kennylevinsen: Fonts would be dealt with by some combination of harfbuzz, pango, fontconfig - or whatever qt decided to use
18:35 kennylevinsen: Not familiar with what font bits X11 might expose on the Xwayland side though
18:54 dviola: I see, for some reason adding fonts like terminus-font makes things a little better, removing it makes it worse
18:55 dviola: by worse I mean, fonts vanish, with terminus-font they're still readable
18:59 soreau: maybe you can compare wayland and x11 backends with a qt app that supports both by setting QT_QPA_PLATFORM
18:59 dviola: I'm puzzled because I can seem to only trigger this when running a wayland session with xwayland, doesn't happen at all if I run e.g. i3 and then sway+xwayland inside of it
19:00 soreau: so it only happens with drm backend, not wayland backend?
19:00 dviola: soreau: with xcb afaik, but yes
19:03 dviola: soreau: i.e. it's fine with QT_QPA_PLATFORM=wayland but not with QT_QPA_PLATFORM=xcb
19:04 dviola: with qt6 it's fine with both, xcb and wayland
19:04 soreau: sounds like a qt5 xcb platform bug then?
19:04 dviola: yeah
19:04 soreau: and it sounds like you have enough to file a qt(5) issue..
19:05 soreau: but since it's working in qt6, maybe the answer is to upgrade to qt6
19:06 dviola: right, thanks
19:06 soreau: 👍
23:21 dviola: I think something on kernel 6.11.6-arch1-1 introduced a regression, now sway on QEMU has the mouse inverted down
23:22 dviola: WLR_RENDERER=pixman makes it go away
23:25 dviola: qemu -device virtio-vga-gl -display gtk,gl=on
23:25 dviola: will need to bisect but I wonder if 6.12 makes it go away