05:44 emersion: PSA: wayland beta is due today
09:06 wlb: wayland-protocols Merge request !305 merged \o/ (ci: don't run pipelines in forks https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/305)
09:06 wlb: wayland-protocols/main: Simon Ser * ci: don't run pipelines in forks https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/f573fa11cf97 .gitlab-ci.yml
10:47 wlb: wayland Merge request !392 opened by Maarten de Vries (de-vri-es) protocol: add compositor defined index to wl_output https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/392
12:00 wlb: weston Issue #906 opened by n3rdopolis (n3rdopolis) If Weston is using simpledrm, and simpledrm is replaced when Weston is inactive, Weston shows a black screen switching back to it https://gitlab.freedesktop.org/wayland/weston/-/issues/906
13:19 vyivel: ping on https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/346?
14:38 IDKmyName: hi
14:46 wlb: wayland/main: Julian Orth * protocol: explicitly describe wl_keyboard state https://gitlab.freedesktop.org/wayland/wayland/commit/9e4f25692792 protocol/wayland.xml
14:46 wlb: wayland Merge request !382 merged \o/ (protocol: explicitly disallow unpaired key events https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/382)
14:52 wlb: wayland/main: Simon Ser * build: bump to version 1.22.92 for the beta release https://gitlab.freedesktop.org/wayland/wayland/commit/f870320958da meson.build
14:53 wlb: wayland New tag: 1.22.92 https://gitlab.freedesktop.org/wayland/wayland/tags/1.22.92
14:57 wlb: wayland.freedesktop.org/main: Simon Ser * releases: add wayland 1.22.92 https://gitlab.freedesktop.org/wayland/wayland.freedesktop.org/commit/72d07eac8bad releases.html
15:56 RandomUser: динаху
15:57 UsingMyPhoneAsAlt: сам йди
15:57 IDKmyName: чо
17:05 DonAlex: Is there any update on being able to map touchscreen inputs to a specific display? It seems it detects touch events fine but applies them only to the primary display which is undesirable.
17:07 daniels: DonAlex: which compositor are you using?
17:10 DonAlex: Gnome
17:14 daniels: DonAlex: you should be able to configure that in GNOME settings - if not please check on their Discourse or file an issue in their GitLab
18:20 DonAlex: @daniels, No settings in Gnome for it. And I did not see any way to do it with gsettings
18:20 mclasen: DonAlex: you should talk to garnacho (who isn't here right now)
18:22 DonAlex: Hmmm
18:23 DonAlex: What timezone are they ?
18:28 daniels: EU
18:31 DonAlex: hmm ok
18:37 RandomUser: exit
21:31 ids1024_: It seems `Xwayland` relies on always getting `wl_keyboard::leave` events, even when it destroys the focused surface. (The `WAYLAND_DEBUG` log for `Xwayland` in that case on `sway` shows a `leave` with a `nil` surface). Otherwise, it doesn't send key up events for keys that were pressed when the surface was destroyed, and the next focus XWayland surface sees them as held down. This
21:31 ids1024_: particular behavior can be fixed by adding 3 lines to Xwayland, but is it correct to expect this from the server? It seems the protocol should be more specific on this.
21:51 ids1024_: It seems odd that a client should rely on getting a `leave` event after it has destroyed the surface, when the `surface` argument of `leave` is not nullable.
21:55 whot: ids1024_: sounds like an xwayland bug tbh, possibly from x assumptions where you get the leave event because the server destroys the windwow for you
22:40 wlb: wayland Issue #465 opened by Ian Douglas Scott (ids1024) Clarify behavior of `wl_keyboard::leave`/`wl_pointer::leave` after client destroys focused surface https://gitlab.freedesktop.org/wayland/wayland/-/issues/465
22:41 ids1024_: Opened an issue. And an Xwayland MR, if it shouldn't be assuming this: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1527
22:41 ids1024_: I think the Wayland protocol spec could definitely be more clear, either way.