Created attachment 138907 [details] debug trace SUMMARY Attaching forced SIGSEGV traceback from gdb SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.90 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-17-lowlatency (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7,6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
I see only a crash in xdg-desktop-portal-kde thanks to some wayland issue. Does it happen all the time? What is your xdg-desktop-portal-kde version?
Sorry, I didn't read your comment properly, your version of xdp-kde is 5.21.90. Does it happen with Plasma 5.22.x?
Ha, i guess this is one of those crashes i filed which are not due to memory segmentation but because i sent signal 11 from htop to the process xdg-desktop-portal-kde. I did this so you can see that the callstack was when it had high CPU usage. I believe there is another bug for the high CPU usage so i've already stopped reporting these crashes. On the other hand, the high CPU usage from xdg-desktop-portal-kde still does appear after each login with Plasma 5.22. I believe this issue with high CPU started way back in 5.21.4. I'm feeling sorry for all the users on Kubuntu 21.04 who still seem to be with 5.21.4 with no backport for them in the official Kubuntu archives. I'm using the kubuntu beta/backport ppa exactly because i was told 5.22 fixes these.
... Just discovered i'm also feeling sorry for myself, i'm on 5.22 and still have the high CPU usage bug. Feel free to close this bug.
Can you kill xdg-desktop-portal-kde after you log in and then start it with QT_LOGGING_RULES='xdp*.debug=true' to see if there is any call/query which might be causing the CPU usage?
I believe this bug should be made a duplicate of this one:https://bugs.kde.org/show_bug.cgi?id=433293
Since then i've switched to Arch and for some time i don't think i see this any more. Kubuntu ships updates at a slower pace. Marking as duplicate. *** This bug has been marked as a duplicate of bug 433293 ***