** Description changed: + [ Impact ] + + Window movements can cause a re-draw of the whole screen. + That causes an unnecessary performance hit, especially noticeable when using a remote session. + 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. + [ Test Plan ] - ## Steps to Reproduce - 1. Set up an Ubuntu VM and log in + 1. Set up an Ubuntu system 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 + 6. Drag a window across the screen + 7. Verify that the red overlay only covers the window rectangle rather than the whole screen + + [ Where problems could occur ] + + mutter is the Wayland compositor library that provides graphics and inputs for the GNOME desktop, thus is a critical component. + Problems could manifest with the action of dragging a window not working anymore, or sudden log-out if gnome-shell crashes.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2080698 Title: Window movements can cause full framebuffer damage Status in Mutter: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Noble: Triaged Status in mutter source package in Oracular: Fix Released Bug description: [ Impact ] Window movements can cause a re-draw of the whole screen. That causes an unnecessary performance hit, especially noticeable when using a remote session. Upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/3630 Upstream fix: https://gitlab.gnome.org/GNOME/mutter/-/commit/030270ba3bf14b23a2d7a5371cf158ff2591f327 [ Test Plan ] 1. Set up an Ubuntu system 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. 6. Drag a window across the screen 7. Verify that the red overlay only covers the window rectangle rather than the whole screen [ Where problems could occur ] mutter is the Wayland compositor library that provides graphics and inputs for the GNOME desktop, thus is a critical component. Problems could manifest with the action of dragging a window not working anymore, or sudden log-out if gnome-shell crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2080698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
