Bug 502178

Summary: The interface elements do not have smooth animations matching the monitor's refresh rate (Wayland)
Product: [Plasma] kwin Reporter: zupnikszydlik
Component: performanceAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: ivan.cukic, leledumbo_cool, nate
Priority: NOR    
Version First Reported In: 6.3.3   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description zupnikszydlik 2025-03-29 21:31:03 UTC
SUMMARY
The interface elements, such as the app launcher, GUI elements on the panel (like notifications, audio volume, or network) and  the overview animation lack smooth transitions that match the monitor's refresh rate. For example, while the monitor runs at 165Hz, the animations are limited to 60 frames per second. 
This issue occurs exclusively on Wayland - on X11, everything runs smoothly.

STEPS TO REPRODUCE
1. Launch panel interface (like application launcher) / Run overview
2. Use GUI to scroll between elements (like 'Applications' and 'Places' in application launcher OR 'Devices' and 'Applications' in audio volume panel). / Use the overview to switch between virtual desktops and move windows across them.

OBSERVED RESULT
GUI animations are capped to 60Hz.
I noticed that moving windows around in the overview is smooth, but the animations for entering, leaving, switching and transferring windows between virtual desktops are capped.

EXPECTED RESULT
GUI animations match monitor's refresh rate.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 6.3.3
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.6.83-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070


ADDITIONAL INFORMATION
Fully updated manjaro system.
I use proprietary NVIDIA drivers v. 570.133.07
Comment 1 Mario Ray Mahardhika 2025-03-31 01:28:49 UTC
Just updated to 6.3.3 and can confirm this issue.

Possible related issue previously fixed (seems to resurface): https://bugs.kde.org/show_bug.cgi?id=485927
Comment 2 Mario Ray Mahardhika 2025-03-31 01:31:44 UTC
Another one (this time it was really fixed, the previous report wasn't AFAICS): https://bugs.kde.org/show_bug.cgi?id=482178
Comment 3 Nate Graham 2025-03-31 20:20:33 UTC

*** This bug has been marked as a duplicate of bug 485927 ***