SUMMARY The full clipboard UI (which is also the same as the Meta+V UI since 6.2) is extremely laggy / slow to respond, compared to other UI elements. Video demonstration: https://cloud.polskalemon.com/s/mWjY4YzeB5cngQL (too large to upload here) STEPS TO REPRODUCE 1. Open the clipboard UI 2. Move the mouse around over its different entries OBSERVED RESULT The UI is extremely slow to respond EXPECTED RESULT The UI responds as quickly as other parts of plasmashell SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS Unstable KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION -
That's very weird, I don't see that at all. Can you mention your hardware setup?
As per neofetch: Host: ASUSTeK COMPUTER INC. ProArt X570-CREATOR WIFI Kernel: 6.11.5-zen1 Uptime: 9 days, 2 hours, 27 mins Packages: 1820 (nix-system), 7998 (nix-user), 45 (flatpak) Shell: zsh 5.9 Resolution: 7680x2160 DE: Plasma 6.2.4 (Wayland) Theme: Breeze Light [Plasma], Breeze-Dark [GTK2], Breeze [GTK3] Icons: breeze [Plasma], breeze-dark [GTK2/3] Terminal: .konsole-wrappe CPU: AMD Ryzen 9 3950X (32) @ 4.762GHz GPU: AMD Radeon RX 7900 XTX GPU: NVIDIA GeForce RTX 3090 Memory: 27348MiB / 64186MiB Note that the NVIDIA GPU is not used to render anything, it's purely reserved for usage within VMs and for CUDA applications (right now, the kernel module isn't even loaded).
Can also confirm on AMD. THe Meta+V popup is less smooth.
As an update, as of 6.3.2, the behavior is much better, but still not what I would expect (now it only stutters when moving the mouse cursor quickly across the entries)
Can you attach a screen recording of that? I don't think I'm able to reproduce it.
> now it only stutters when moving the mouse cursor quickly across the entries aaaaa this is an AMD GPU driver bug, either https://gitlab.freedesktop.org/drm/amd/-/issues/3760 or one of the related ones. I encounter it myself. You can work around it by adding "amdgpu.dcdebugmask=0x200" to your kernel boot args. That did it for me.
*** Bug 501096 has been marked as a duplicate of this bug. ***