05:25 <wlb> wayland Issue #249 opened by () Wayland cross compilation for arm toolchain https://gitlab.freedesktop.org/wayland/wayland/-/issues/249

10:00 <ifreund> > The edges parameter specifies how the surface should be resized, and is one of the values of the resize_edge enum.

10:00 <ifreund> I don't see a matching protocol error enum value for the compositor to use if the client violates this...

10:00 <ifreund> or is it not intended to be a protocol error? Should the compositor just ignore the request if the resize_edge is invalid?

10:44 <emersion> i think we're missing a proto error

10:47 <wlb> wayland Issue #250 closed \o/ (Place window to specific location. https://gitlab.freedesktop.org/wayland/wayland/-/issues/250)

10:48 <wlb> wayland Issue #249 closed \o/ (Wayland cross compilation for arm toolchain https://gitlab.freedesktop.org/wayland/wayland/-/issues/249)

10:50 <ifreund> Alright, I'll open an MRA

10:50 <ifreund> *MR

10:51 <DemiMarieObenour[m]> Should there be an error for “protocol didn’t specify anything better”?

10:53 <ifreund> I'd say no, that would cause these things to go unfixed for longer

10:54 <wlb> wayland Issue #20 closed \o/ (Raw, HID and Direct libInput Protocol. https://gitlab.freedesktop.org/wayland/wayland/-/issues/20)

10:54 <wlb> wayland-protocols Issue #66 opened by () Raw, HID and Direct libInput Protocol. https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/66

10:54 <wlb> wayland-protocols Issue #67 opened by () Centered/Splash shell surfaces https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/67

10:54 <wlb> wayland Issue #40 closed \o/ (Centered/Splash shell surfaces https://gitlab.freedesktop.org/wayland/wayland/-/issues/40)

10:56 <wlb> wayland Issue #16 closed \o/ (Syscall param sendmsg(msg.msg_iov[0]) points to uninitialised byte(s) https://gitlab.freedesktop.org/wayland/wayland/-/issues/16)

10:58 <wlb> wayland Issue #35 closed \o/ (broken man pages in wayland-1.12.0 https://gitlab.freedesktop.org/wayland/wayland/-/issues/35)

10:59 <wlb> wayland Issue #31 closed \o/ (Can't build with LLVM/clang https://gitlab.freedesktop.org/wayland/wayland/-/issues/31)

11:00 <wlb> wayland Issue #11 closed \o/ (Determine endianess of wl_shm pixel format codes https://gitlab.freedesktop.org/wayland/wayland/-/issues/11)

11:01 <wlb> wayland-protocols Merge request !123 opened by () xdg-shell: add invalid_resize_edge error value https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/123

11:02 <wlb> wayland-protocols Issue #68 opened by () Add device FD to zwp_linux_dmabuf_v1 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/68

11:02 <wlb> wayland Issue #59 closed \o/ (Add device FD to zwp_linux_dmabuf_v1 https://gitlab.freedesktop.org/wayland/wayland/-/issues/59)

11:11 <wlb> wayland Merge request !187 opened by () protocol: wl_shm uses pre-multiplied alpha https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/187

11:12 <wlb> wayland/shm-premult: Build #436321 failed after 21 seconds https://gitlab.freedesktop.org/wayland/wayland/pipelines/436321

11:14 <wlb> wayland Issue #81 closed \o/ (CI test on armhf and aarch64 https://gitlab.freedesktop.org/wayland/wayland/-/issues/81)

11:14 <wlb> wayland-protocols Issue #69 opened by () Protocol Extension for VRR in Fullscreen Use (FreeSync, Variable Refresh Rate) https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/69

11:14 <wlb> wayland Issue #84 closed \o/ (Protocol Extension for VRR in Fullscreen Use (FreeSync, Variable Refresh Rate) https://gitlab.freedesktop.org/wayland/wayland/-/issues/84)

11:16 <wlb> wayland Issue #166 closed \o/ (Support HDR https://gitlab.freedesktop.org/wayland/wayland/-/issues/166)

11:16 <wlb> wayland-protocols Issue #70 opened by () Support HDR https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/70

21:43 <jpoiret> Hi! I'm trying to set up vaapi on wayland, and when i run 'vainfo' on weston and sway, I get "wl_drm@6: error 0: authenticate failed". I'm struggling to grasp what library/client/server is responsible for this error (haven't looked much into the intricacies of the wayland protocol). Any hints of where this might come from?

21:53 <emersion> hm i think it needs a newer libva

21:56 <wlb> wayland-protocols Merge request !124 opened by () Draf: Create zext-screencopy-unstable-v1 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/124

21:59 <wlb> wayland-protocols Merge request !39 closed (WIP: Add the cursor-spy protocol)

22:00 <jpoiret> emersion: seems i'm using libva 2.13

22:02 <jpoiret> oh, but not compiled with the latest mesa, i'll do that first

22:02 <zebrag> hi, external keyboard working in tty, not working (lost) in wayland session after inactivity

22:03 <emersion> hm 2.13 should be fine

22:04 <zebrag> it's usb keyboard, it's listed by lsusb, it was working at session start, then stopped working after long inactivity

22:04 <zebrag> builtin (laptop) keyboard still working

22:09 <ifreund> any1: I believe that protocol should be just ext-screencopy-v1 with the new naming scheme

22:16 <any1> New naming scheme? When did that happen?

22:19 <ifreund> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/55

22:25 <zebrag> I had a hard time having the keyboard working again. The device is "ID 046a:0008 Cherry GmbH Wireless Keyboard and Mouse". I'd disabled the mouse via the settings. It's possible wayland (?) is mixing up the mouse and the keyboard.

22:25 <zebrag> Initially, the keyboard was working with the mouse disabled

22:26 <zebrag> But then after a long idle time, the keyboard stopped working.

22:27 <zebrag> I couldn't have it working again, even unplug/plug, until I reenabled the mouse. Then it did work again after unplug/plug

22:27 <zebrag> It was working alright in tty and to type login in sddm/xorg

23:12 <DemiMarieObenour[m]> Is it possible for an implementation of StatusNotifierHost to be an ordinary Wayland client using xdg-shell, or does it need privileges?