Hi all, the reasons leading to the Won't fix status are invalid. This bug is present today in Plucky on both Wayland and X. Please see attached screenshot on Plucky running Wayland. I created it by suspending the laptop while running at 100% scale on an external monitor, then waking it up on the local screen at 200%.
** Attachment added: "Border corruption bug on Wayland. Signal app over Firefox search bar. Green boxes are redacted personal information that are irrelevant to the bug." https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1924689/+attachment/5885141/+files/Screenshot%20From%202025-06-19%2008-37-53%20redacted.png -- 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/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Won't Fix Status in mutter source package in Noble: Triaged Status in mutter source package in Oracular: Won't Fix Status in mutter source package in Plucky: Triaged Status in mutter source package in Questing: Won't Fix Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+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
