02:30wlb: wayland-protocols Merge request !252 opened by Jonas Ådahl (jadahl) Migrate selected protocols from unstable/ to staging/ https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/252
05:55Riolku: Writing a client targeting wlr-layer-shell-unstable-v1, after an output has its mode changed, sway seems to be sending a configure() event for the previous mode. Specifically, if I change a headless output from 960x540 to 1920x1080, sway emits a configure event, but with the old 960x540 resolution.
05:56Riolku: It properly emits a `mode` event with the updated resolution... should I be listening to that instead? I feel like I'm missing something
06:35emersion: no, the mode should not be used here
06:36emersion: can you obtain a WAYLAND_DEBUG=1 log?
10:39wlb: weston/main: Marius Vlad * neatvnc.wrap: Update to neatvnc 0.7.0 https://gitlab.freedesktop.org/wayland/weston/commit/4d633dd0b216 subprojects/neatvnc.wrap
10:39wlb: weston Merge request !1371 merged \o/ (neatvnc.wrap: Update to neatvnc 0.7.0 https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1371)
12:44wlb: wayland-protocols/main: Simon Ser * build: simplify dict loops https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/78e38c57bf2e meson.build
12:44wlb: wayland-protocols/main: Simon Ser * build: add version for stable protocols https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/a113a93d83ba meson.build
12:44wlb: wayland-protocols/main: Simon Ser * linux-dmabuf: mark as stable https://gitlab.freedesktop.org/wayland/wayland-protocols/commit/51bee6e074de stable/linux-dmabuf/README stable/linux-dmabuf/feedback.rst stable/linux-dmabuf/linux-dmabuf-v1.xml meson.build unstable/linux-dmabuf/README unstable/linux-dmabuf/linux-dmabuf-unstable-v1.xml
12:44wlb: wayland-protocols Merge request !223 merged \o/ (linux-dmabuf: mark as stable https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/223)
13:07pq: woo \o/
14:16AnuthaDev: hlo
14:16AnuthaDev: Hello! I was looking through X.org EVoC ideas page and found the "KMS terminal emulator" project under wayland interesting. Can I please get a rough idea of where to start if I want to work on this project under EVoC?
14:16AnuthaDev: I have some experience in C and linux scripting, not much with the kernel itslef though I have succesfully compiled it a few times :P
14:19pq: oh wow, especially the Weston section there needs a clean-up
14:21pq: I wonder if the stand-alone KMS terminal is relevant today... it seems one would achieve the same by choosing a kiosk-mode Wayland compositor and any Wayland terminal emulator to run fullscreen on it.
14:21pq: nerdopolis, do you have an opinion?
14:22pq: given that nerdopolis might be the person that has looked into CONFIG_VT=n systems the most, IIRC
14:31emersion: yeah, i think existing compositor + existing terminal makes a lot of sense
14:32pq: should we just drop the idea from https://www.x.org/wiki/SummerOfCodeIdeas/ then?
14:34Riolku: emersion: After some more investigating, it's because of my use of `set_size`. I thought I needed to call that with the size given in the first configure() call, but it appears I should instead call set_size(0, 0)
14:37AnuthaDev: Well, unfortunate
14:38pq: AnuthaDev, yeah, sorry.
14:39AnuthaDev: Is there any idea on that page that you'd recommend ?
14:39AnuthaDev: Like which project is the most relevant/required currently?
14:42pq: I don't know really. I only know about Weston, and the "multiple KMS devices" is already implemented.
14:43pq: "Weston timeline debugging" might not be good as-is, but expanding the scope to figuring out how performance profiling in general is done nowadays and seeing what could be done there, maybe.
14:45pq: Perfetto something maybe?
14:49pq: AnuthaDev, perhaps an even more important question is finding a mentor.
14:52AnuthaDev: Yeah, I guess I should find a mentor first, since all this is very new for me
14:52AnuthaDev: The only knowledge I have is from zmike's blog :-)
14:53zmike: hired.
14:54jadahl: super. good. mentor.
14:54AnuthaDev: Hello !!!
14:56AnuthaDev: Your blog is my inspiration
14:57AnuthaDev: I became interested in GPU+kernel development after following the asahi project and your blog
14:58pq: sounds like you have a couple of people you could contact for ideas already :-) It doesn't have to be from the EVoC ideas wiki page.
14:58zmike: thanks, always great to hear I'm inspiring new driver developers
14:58emersion: zmike, head of marketing department
15:14AnuthaDev: Thanks for the help everyone, I'll be emailing some people now :-)
21:13wlb: wayland Merge request !342 opened by Max Verevkin (MaxVerevkin) protocol: add wl_pointer.warp https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/342