10:18 wlb: wayland-protocols/main: Simon Ser * xdg-output-unstable-v1: deprecate name and description https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/380bdd6ba7ed unstable/xdg-output/xdg-output-unstable-v1.xml
10:19 wlb: wayland-protocols Merge request !189 merged \o/ (xdg-output-unstable-v1: deprecate name and description https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/189)
19:04 DodoGTA: Wayland should really provide safeguards against "error in client communication" error
19:07 emersion: what do you mean?
19:12 DodoGTA: Firefox crashed 2 times already when using the Developer Tools Inspector because of that
19:13 emersion: it's a firefox bug
19:13 emersion: it means firefox doesn't follow the protocol, so can't continue to use the wayland connection
19:14 DodoGTA: That error appeared with no other context in the systemd journal
19:15 DodoGTA: If that's the app's fault what would be the best practices to avoid that error from occuring?
19:15 emersion: that's because GTK doesn't print the error
19:18 DodoGTA: I saw kwin_wayland_wrapper as the tag, so I really have to restart the compositor with WAYLAND_DEBUG to diagnose the issue?
19:18 emersion: no, you can start the client with that flag
19:18 emersion: s/flag/env var/
19:23 DodoGTA: There's just some wl_pointer calls before Gdk says it lost connection to the Wayland compositor
19:28 DodoGTA: Which is so mysterious
19:36 DodoGTA: But I remember someone said something about the socket buffer filling up
19:42 DodoGTA: Weird curiosity: What would happen if I `cat` the Wayland socket?
20:01 bl4ckb0ne: or you can use WAYLAND_DEBUG=1