SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** In Plasma 6 Beta 1, all animations work smoothly except for the new Overview feature, which exhibits noticeable frame rate drops, resulting in laggy user input. STEPS TO REPRODUCE 1. Update Fedora Kinoite to the latest rawhide version. Use a clean image without any layered packages. 2. Open the Overview by pressing the Meta + Tab. 3. Observe the animation performance. OBSERVED RESULT The animation in the Overview is laggy and not smooth. EXPECTED RESULT The animation in the Overview should be as smooth and responsive as others. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 40 Kinoite (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION - Graphics Card: AMD Radeon Graphics - Rawhide Build: Rawhide.20231220.n.0
Very likely a combination of bug 476002 and bug 455585. What's your screen resolution, refresh rate, and scale factor?
(In reply to Nate Graham from comment #1) > Very likely a combination of bug 476002 and bug 455585. What's your screen > resolution, refresh rate, and scale factor? Thank you for the reply. Resolution: 2160x1440 (3:2) Scale: 100% Refresh Rate: 60Hz Additionally, during my testing today, I checked journalctl and found it reporting multiple errors related to the digital clock and AMD GPU, although there were no crashes. I think these lines are connected to the overview issue, as they appear every time I enter the new overview. ``` Dec 21 16:29:15 fedora kwin_wayland_wrapper[15310]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Dec 21 16:29:15 fedora kwin_wayland_wrapper[15310]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Dec 21 16:29:15 fedora kwin_wayland[15310]: QSqlDatabasePrivate::database: requested database does not belong to the calling thread. Dec 21 16:29:15 fedora kwin_wayland[15310]: kde.plasma.activitiesstats: PlasmaActivities: Database is not open: "" "" QSqlError("", "Driver not loaded", "Driver not loaded") Dec 21 16:29:15 fedora kwin_wayland[15310]: kde.plasma.activitiesstats: Plasma Activities ERROR: There is no database. This probably means that you do not have the Activity Manager running, or that something else> Dec 21 16:29:15 fedora kwin_wayland[15310]: QObject::startTimer: Timers cannot be started from another thread Dec 21 16:29:17 fedora kwin_wayland[15310]: QObject::killTimer: Timers cannot be stopped from another thread ``` The logs indicate a driver missing issue, so I layered mesa-va-drivers-freeworld from RPM Fusion, but the error persists. ``` Dec 21 17:00:48 fedora kwin_wayland_wrapper[1754]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Dec 21 17:00:48 fedora kwin_wayland_wrapper[1754]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Dec 21 17:00:49 fedora kwin_wayland[1754]: QObject::startTimer: Timers cannot be started from another thread Dec 21 17:00:50 fedora kwin_wayland[1754]: QObject::killTimer: Timers cannot be stopped from another thread ``` I also encountered multiple errors related to the digital clock, though they don't seem to be related to the overview issue. ``` Dec 21 16:24:48 fedora plasmashell[15510]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78: TypeError: Type error ```
The same error after I layered mesa-vdpau-drivers-freeworld. ``` Dec 21 17:29:17 fedora kwin_wayland_wrapper[1754]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Dec 21 17:29:17 fedora kwin_wayland_wrapper[1754]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13) Dec 21 17:29:17 fedora kwin_wayland[1754]: QSqlDatabasePrivate::database: requested database does not belong to the calling thread. Dec 21 17:29:17 fedora kwin_wayland[1754]: kde.plasma.activitiesstats: PlasmaActivities: Database is not open: "" "" QSqlError("", "Driver not loaded", "Driver not loaded") Dec 21 17:29:17 fedora kwin_wayland[1754]: kde.plasma.activitiesstats: Plasma Activities ERROR: There is no database. This probably means that you do not have the Activity Manager running, or that something else > Dec 21 17:29:17 fedora kwin_wayland[1754]: QObject::startTimer: Timers cannot be started from another thread Dec 21 17:29:18 fedora kwin_wayland[1754]: QObject::killTimer: Timers cannot be stopped from another thread ```
Similar error on another Intel laptop. Resolution: 2560x1600 (16:10) Scale: 100% Refresh Rate: 60Hz & 90Hz & 120Hz ``` Dec 21 18:19:29 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot be started from another thread Dec 21 18:19:30 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be stopped from another thread Dec 21 18:19:31 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot be started from another thread Dec 21 18:19:32 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be stopped from another thread Dec 21 18:19:32 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot be started from another thread Dec 21 18:19:33 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be stopped from another thread Dec 21 18:19:33 fedora kwin_wayland[1659]: QSqlDatabasePrivate::database: requested database does not belong to the calling thread. Dec 21 18:19:33 fedora kwin_wayland[1659]: kde.plasma.activitiesstats: PlasmaActivities: Database is not open: "" "" QSqlError("", "Driver not loaded", "Driver not loaded") Dec 21 18:19:33 fedora kwin_wayland[1659]: kde.plasma.activitiesstats: Plasma Activities ERROR: There is no database. This probably means that you do not have the Activity Manager running, or that something else is broken on your system. Recent documen> Dec 21 18:19:33 fedora kwin_wayland[1659]: QObject::startTimer: Timers cannot be started from another thread Dec 21 18:19:34 fedora kwin_wayland[1659]: QObject::killTimer: Timers cannot be stopped from another thread ```
The issue still exists in Beta 2 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 40 Kinoite (available in About System) KDE Plasma Version: 5.91.0 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Rawhide Build: Rawhide.20231229.n.0
With 100% scale (and a 60hz refresh rate in one reproducing case), I think this is likely to be a driver problem and not a performance issue in the effect itself. Can you attach a video or screen recording that shows the problem, so we can gauge what level of frame drop you're experiencing?
(In reply to Nate Graham from comment #6) > With 100% scale (and a 60hz refresh rate in one reproducing case), I think > this is likely to be a driver problem and not a performance issue in the > effect itself. > > Can you attach a video or screen recording that shows the problem, so we can > gauge what level of frame drop you're experiencing? The framedrop is always and most observable when enter and leave overview. It drops from ~60 to ~30 when I enter overview. It then jumps between 60 to 30 when I'm in overview. If I move the any window inside overview, it goes back to 60. If I stop the input, framerate starts to jump again. Sorry for my late reply. I cannot get screen recording and show the framerate drop. It seems doing screen recording from OBS Studio somehow fix the issue. I can use Show FPS in Desktop Effect to display the current FPS though. In Plasma 6 RC1 (Rawhide.20240117.n.0), it is much improved compare to beta1 but little difference compare to beta2. The error message I reported in previous post does not seem to appear anymore.
Thanks. If a screen recording doesn't show it, maybe try a phone video?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!