SUMMARY cursor movements and plasma animations lag weirdly on my system while Discover app store is running. I enabled Show FPS effect in Desktop Effects kcm, it indicates that the framerate decreases to 15 while Discover is running and I move cursor. When Discover is not running, framerate is 60fps. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.15.1 KDE Frameworks Version: 5.55.0 Qt Version: 5.12.1 Kernel Version: 4.20.10-arch1-1-ARCH
Can you try with another kirigami app? like the kirigami gallery, for example.
I can't reproduce the problem using kirigami gallery. I have just noticed that framerate only decreases while Discover window is maximized and not minimized.
This problem persists. Now it only occurs while I move cursor on maximized Discover window. Framerate is 60 fps if Discover is maximized and focused but cursor is stopped. Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0 beta2 Kernel Version: 5.0.9-arch1-1-ARCH
This bug is still happening when I move cursor on the lists of installed or featured apps, no matter if Discover window is maximized or not. No problem when I move the cursor on the side bar or on "About" or "Sources" pages.
*** Bug 409035 has been marked as a duplicate of this bug. ***
As we can read in bug 409035 marked as duplicate, system settings is also affected. What is the correct product for this bug?
If I launch intel_gpu_top on my ironlake GPU, the Render/3D/0 row reaches 100% when I move my mouse around to quickly trigger these fade-in fade-out animations when these apps (discover and system settings) are maximized on a FHD monitor. If I trigger what looks like the same kind of animations in dolphin, it stays under 3%.
It seems that my bug 409035 concerns QtQuick apps and the fact that they are using Opengl to render everything. They make my Ironlake GPU hit 100% very easily. If I force the software backend, the desktop is fluid again. It is very likely that my GPU is too weak. But it may also come from the apps, QtQuick, or the driver. I am not sure how to debug this. In the meantime, I am using QT_QUICK_BACKEND=software as a workaround.
Yeah this is a general problem with really weak GPUs. :/
*** Bug 423935 has been marked as a duplicate of this bug. ***