** Description changed: Upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/3630 Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/commit/030270ba3bf14b23a2d7a5371cf158ff2591f327 + This should be patched in Noble. - This should be patched in Noble. + ## Steps to Reproduce + 1. Set up an Ubuntu VM and log in + 2. Launch the Looking Glass debugger by pressing `Alt+F2`, typing `lg`, and pressing Enter + 3. Navigate to the "Flags" tab in the top right corner of the debug window + 4. Scroll down and enable the `PAINT_DAMAGE_REGION` flag. By enabling this flag, a red overlay will appear to show regions where the screen is being redrawn and helps visualize framebuffer damage. + 5. Proceed to reproduce the issues listed in this bug report by performing actions such as: + - Opening a new window + - Dragging a window across the screen + - Resizing any window + - Changing window stacking order
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2080698 Title: Window movements can cause full framebuffer damage To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2080698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
