Running weston with the headless backend will segfault if wl_event_loop_add_timer fails (eg if timerfd is not enabled in the kernel) since https://github.com/wayland-project/weston/blob/42c0e14808bfd39e1a2eea34f43f0b5fe20fbb16/libweston/compositor-headless.c#L160 never checks if the returned result is NULL.
Hi, sure, we could turn that into an explicit abort().
Adding a fallback path would not be feasible or desirable.
Yes, I was just thinking that it might be nicer if there was some kind of error message to avoid needing to break out gdb... something like at https://github.com/wayland-project/weston/blob/42c0e14808bfd39e1a2eea34f43f0b5fe20fbb16/compositor/main.c#L1928?
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/102.