499962 2025-02-13 07:37:20 +0000 Programs using Chromium failed to perform Toggle Present Windows 2025-02-19 02:02:26 +0000 1 1 4 Plasma kwin effects-window-management 6.3.0 Arch Linux Linux RESOLVED DUPLICATE 499987 NOR normal --- 0 duandongyi2019 kwin-bugs-null cwo.kde 0 oldest_to_newest 2397429 0 duandongyi2019 2025-02-13 07:37:20 +0000 SUMMARY Programs using Chromium, such as Chrome and VSCode, experience issues when using "Toggle Present Windows" under Wayland and screen scaling mode. These issues include failure to function, severe frame drops, and stuttering. STEPS TO REPRODUCE 1. Open a Chrome or vscode in wayland 2. Press Ctrl + F10 OBSERVED RESULT Sometimes failure to function, Sometimes severe frame drops EXPECTED RESULT Works same as KDE plasma 6.2.5 SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: 6.3.0 KDE Plasma Version: 6.3.0 KDE Frameworks Version: Qt Version: 6.8.2 ADDITIONAL INFORMATION Launch app in xwayland mode does not make it functions too 2397431 1 duandongyi2019 2025-02-13 07:55:04 +0000 KDE Frameworks Version is 6.10.0 If you need anything else please let me know 2397432 2 duandongyi2019 2025-02-13 07:57:57 +0000 After setting the screen from 1080p/125% and 4K/200% to 1080p/100% and 4K/100%, it works properly. 2398780 3 duandongyi2019 2025-02-17 07:18:54 +0000 Correction: This issue occurs if and only if a 4K display is set to a resolution and scaling of 200% or higher. 2398783 4 duandongyi2019 2025-02-17 07:29:37 +0000 And if i disable all other displays but the 4k/200%, It works properly 2398787 5 duandongyi2019 2025-02-17 07:59:21 +0000 Oh I figue it out! Turn off the night light mode will make it works properly even with 4k/200% with two 1080p / 125% display, The night light mode is the trigger 2398854 6 cwo.kde 2025-02-17 10:50:25 +0000 If it is fixed by turning off Night Light, I would guess it's the same cause as bug 499987; see also bug 500021 where turning off Night Light improved performance. This should be fixed in 6.3.1, releasing tomorrow, so please reopen if it still happens after you upgrade to that version. *** This bug has been marked as a duplicate of bug 499987 *** 2399881 7 duandongyi2019 2025-02-19 02:02:26 +0000 Yes, This bug is fixed in 6.3.1, Thanks.