01:50wlb: wayland Issue #500 closed \o/ (a wl_display cannot be intergrated into another event loop using wl_event_loop_get_fd https://gitlab.freedesktop.org/wayland/wayland/-/issues/500)
08:49wlb: weston Issue #961 opened by () weston-9 crash on page_flip_handler when system suspend/resume https://gitlab.freedesktop.org/wayland/weston/-/issues/961
10:15wlb: weston Merge request !1630 closed (libweston: use Requires in pkg-config file)
10:54wlb: weston Issue #962 opened by () Weston systemd manual - No active login service https://gitlab.freedesktop.org/wayland/weston/-/issues/962
14:08emersion: zzag: have you seen this? https://github.com/Ferdi265/wl-restart/issues/2
14:08emersion: i agree the naming isn't super consistent, --socket isn't very descriptive (--wayland-display would be better)
14:09emersion: my own preference would probably be LISTEN_FDS since it's the closest to a standard as we're going to get, or CLI flags with better naming
14:11d_ed[m]: we have a WIP with LISTEN_FDs. Not sure how that would work with changing the service though
14:11d_ed[m]: I had not seen that though, thanks for sharing
14:13emersion: it would be nice to agree on a LISTEN_FDS scheme
14:14emersion: what to pick for the FD name? how to pass the WAYLAND_DISPLAY?
14:14emersion: should the FD name be "wayland", and the WAYLAND_DISPLAY already set?
14:14emersion: should the FD name contain the future WAYLAND_DISPLAY value?
14:15emersion: (i'd say probably the former would make more sense?)
18:00wlb: wayland-protocols Merge request !355 opened by () tray-v1: Add new protocol https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/355
18:06Ermine: is wlb supposed to show who have opened the request?
18:06vyivel: yes
21:21soreau: Running weston-simple-egl shows a surface with a triangle but it no longer spins as it did before, even with a known working mesa commit
21:21soreau: the compositor is wayfire with wlroots 0.18.2 and everything else seems to be working ok
21:23soreau: 0.18.1* (even though pkg-config --modversion says 0.18.0)
21:26soreau: WAYLAND_DEBUG shows this until sending SIGINT: https://termbin.com/0p2x
21:27llyyr: check what strace says?
21:29ManMower: frame callback never completed?
21:34soreau: llyyr: this is the tail end of it https://pastebin.com/raw/5xA3JVhU
21:34soreau: not sure if there are more interesting parts
21:34soreau: ManMower: wym?
21:35soreau: I would expect the compositor is sending frame events if everything else is working..
21:35ManMower: I don't see a frame callback in your pastebin
21:35ManMower: I see the request, but no event. and weston-simple-egl won't render the next frame until it gets it
21:35soreau: well.. maybe that's the problem then
21:36ManMower: but... weston-simple-shm should break without that too, I'd think
21:36soreau: lemme see
21:36ManMower: I would've expected very many things to be broken if frame callbacks aren't working in general
21:36soreau: simple-shm works for animation at least
21:36soreau: ManMower: yea same
21:36ManMower: interesting
21:37ManMower: your strace seems to indicate the display flush occurred.
21:38soreau: oh you know..
21:38soreau: hm
21:38soreau: well no
21:38ManMower: can you dump a stack trace from gdb after weston-simple-egl falls down a hole? curious as to where it's sitting
21:38llyyr: maybe stupid, but does eglgears work?
21:39soreau: derp
21:39soreau: I went to update weston and realized I had some stupid patch applied
21:39soreau: for reasons I am not sure
21:39soreau: but it works now :P
21:39ManMower: phew. :)
21:40soreau: llyyr: ManMower: thanks for reading, I'll go finish my other foot in the corner now ;)
21:41ManMower: :D
22:43DemiMarie: Would it make sense for a compositor to be socket-activated?
23:53Ermine: I see that as "I'm trying to launch a gui app from console, and it starts along with the compositor". I don't see the point, but it will look cool on the first time
23:54Ermine: Though KWin people somehow tried to use that mechanism to allow restarting the compositor in case of crash. Idk if they are actually using it