@ Daniel van Vugt, The faulty change has a timestamp of 22 Feb, and the package began to arrive at users probably on 29 Mar. That's a difference of 5 weeks.
I'm not familiar with Ubuntu's internal procedures, I don't know how things work, which component (e.g. building packages, QA, somewhat wider testing in -proposed etc.) took how long, but overall 5 weeks is pretty long. As I understand from comments in upstream mutter#3384, it's not immediately obvious to you guys what and why exactly goes wrong and how to properly fix all this. It needs investigation first. This means that my rough guess is that, if everything goes well, it could take maybe 1-2 weeks to develop a fix and another 5 weeks for the regular release prodecure? Do you have any wild estimate on how many people were affected by the old bug that this update fixed, and how many are affected by the new one? The old one seems to be about software rendering, i.e. when running inside a virtual machine. The new one seems to affect people using an NVidia video card with its proprietary driver. Sounds to me that the new issue probably affects way more people. I'm wondering: Is there some guideline, best practice, runbook rule etc. describing how to handle such a situation? If so, what does it say? Wouldn't the right thing be to release new updated packages that revert this change ASAP (like, in a day or two at most, skipping QA and -proposed etc.), and then start to work on the proper fix that fixes both issues at the same time? -- 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 in native terminal on Nvidia desktops with X11 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
