03:10 newbthenewbd: https://drive.google.com/file/d/1kagHFRtudb_V8t73-4rhF2WAIfcxSEig/view managed to record my-yesterday's quirk near the end of the video and otherwise another, wrongly detects pinches
03:12 newbthenewbd: whot pls :( am open to long walks thru the logs, debugging tools, code and other cliches :)
09:00 leon-anavi: mvlad, pH5 thank you for your help. After generating certificates with correct hostname I was able to connect vinagre over VNC to my embedded device with rk3399 and Weston 12.
09:00 whot: newbthenewbd: I'm at a conference this week, really hard to do this synchronously, best to file a bug, sorry
09:01 mvlad: leon-anavi, nice, thanks for the follow-up.
09:02 newbthenewbd: whot: I wasn't sure if it was worth a bug lol, well have a nice time over there and thanks a lot for libinput!
10:35 newbthenewbd: mm took a little more look, so if I just added the wacom here... https://gitlab.freedesktop.org/libinput/libinput/-/blob/main/src/evdev-mt-touchpad.c?ref_type=heads#L2921 seems like the very same thing
10:37 bittin_guadec: https://www.youtube.com/watch?v=dVVyokoQl2k
10:41 MrCooper: whot's talk about libei is live
10:46 newbthenewbd: that's a great talk :o now I didn't even manage to start that recompile
10:48 bittin_guadec: MrCooper, so it is
10:49 bittin_guadec: newbthenewbd, sorry :p
13:38 MrCooper: has any wayland-protocols proposal ever been explicitly nacked?
13:50 emersion: DRM stuff maybe
13:53 MrCooper: no GitLab MR or issue has the Nacked label, maybe it happened earlier on the mailing list though?
13:55 emersion: in général there is no need to explicitly NACK
13:55 emersion: hrm phone autocorrect
13:56 d_ed[m]: There's definitely protocols with people saying "I wouldn't accept blah blah blah"
13:56 emersion: just giving feedback early is enough to avoid this problem in almost all cases
13:56 d_ed[m]: and then a lot of death by silence
13:56 emersion: yeah, but that's not an explicit, formal NACK
13:56 emersion: yea
16:36 istasi: Hello, im an newbie, and im unsure as to where i should or if i should report an issue im encountering, everytime i put my pc to sleep, when it comes up again, the GUI is locked up, with mouse leaving a trail behind, it only happens when im using wayland kde, not when im using x11 kde, https://gitlab.freedesktop.org/wayland/wayland/-/issues/new this says its more likely an issue with the compositor but i dont know enough to continue
17:28 wlb: wayland Issue #401 opened by darkk99 (darkk99) (Suggestion) Add raw mouse input support https://gitlab.freedesktop.org/wayland/wayland/-/issues/401
17:34 wlb: wayland Issue #401 closed \o/ ((Suggestion) Add raw mouse input support https://gitlab.freedesktop.org/wayland/wayland/-/issues/401)