The Resolute task is still New, while Stonking is Fix Committed and milestoned for ubuntu-26.10 and the upstream task is Fix Released.
Resolute is the LTS, and it is where this hurts most: the failure mode is a global OOM that takes the session down, not a visual glitch. 26.04.1 currently ships libmutter-18-0 / mutter-common 50.1-0ubuntu2.2 and gnome-shell 50.1-0ubuntu1.2, so the fix is not present. With the [nvidia] prefix now dropped from the title, the scope isn't driver-specific either: upstream #4101 has reproductions on amdgpu, i915 and xe. The backport already exists on the stable branch. af0c9808 and its two dependencies (83c465ff, c145106d) landed on gnome-50 via !5325 and shipped in the 50.5 tag, so this does not need a hand-rolled cherry-pick from main. Is anything missing from the SRU template above for the Resolute task to move? I can verify from resolute-proposed on hybrid Intel + NVIDIA proprietary with mixed-resolution outputs. It reproduces here in under two minutes and I already have baseline numbers on the broken version, so verification would be same-day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167374 Title: gnome-shell leaks scanout dma-bufs while locked (fixed in mutter 50.5) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2167374/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
