I’ve now had the time to look into the offending change, why it exists and how Ubuntu wants to release it. The change exists, currently, in support of Xwayland 24.1 to get legacy apps rendering correctly in Nvidia Wayland sessions. That’s something Ubuntu plans to do in 24.10 but no sooner. Not just because of the recency of Xwayland 24.1, but because it also doesn’t work correctly without Nvidia driver 555 which is still in beta and not even in Oracular yet.
So it’s a yes for 24.10 and a no for 24.04. That is unless some day in 24.04.x we find ourselves with Xwayland >= 24.1 and nvidia-graphics-drivers-[>=555] in Noble. Then we might reconsider.
For now I would like to propose a small modification to Mutter 46.2 that I hope will allow it to flow into Noble updates:
--- a/src/wayland/meta-wayland.c
+++ b/src/wayland/meta-wayland.c
@@ -873,7 +873,6 @@ meta_wayland_compositor_new (MetaContext *context)
meta_wayland_activation_init (compositor);
meta_wayland_transaction_init (compositor);
meta_wayland_idle_inhibit_init (compositor);
- meta_wayland_drm_syncobj_init (compositor);
meta_wayland_init_xdg_wm_dialog (compositor);
#ifdef HAVE_WAYLAND_EGLSTREAM
This prevents the new logic from being initialised, advertised or usable by Wayland clients including Xwayland. And crucially it would be a trivial patch we can put on top of Mutter 46.2 paving the way for Noble to receive all future Mutter point releases without risk of conflict.
@raof, since you’re the SRU team member with this particular domain knowledge I am proposing this to you first before commencing any work in Salsa. Edit: Also @tjaalton in case you’re interested 