I agree the time delay was unacceptable here. Although I did write the fix immediately, it got stuck in red tape and an element of bad luck.
The offending change could not be rolled back because it fixed an issue for a major partner as mentioned in comment #23. For most of May I was away (work and vacation), thinking the fix was ready and heading for release, with nothing left to do. Turns out that was wrong because there was a spurious test failure holding it up. I failed to dig deep enough to notice that blockage existed. It looks like "Ubuntu SRU Bot" might have failed to send us enough notifications to tell when the main holdup actually happened. I'm not sure. Other reasons this bug didn't move faster are: * The entire team was busy focussing on the 24.04 release * The entire team was also travelling during May * Most Canonicalers don't use Nvidia * Those who do use Nvidia might not have noticed the bug (like myself when I started investigating it) I don't think there's any way I could have given this more eyeballs during May, but I have personally learned to make to sure open the correct "excuses" tracking page and be more proactive in checking there are no silent test failures lurking in the background holding up an SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059847 Title: Input lag or freezes on Nvidia desktops with X11 after logging "MetaSyncRing: Sync object is not ready -- were events handled properly?" To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2059847/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
