https://bugs.kde.org/show_bug.cgi?id=437911
Lyubomir changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=437911
--- Comment #6 from Lyubomir ---
I believe this bug should be made a duplicate of this
one:https://bugs.kde.org/show_bug.cgi?id=433293
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437911
--- Comment #5 from Jan Grulich ---
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?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=437911
--- Comment #4 from Lyubomir ---
... 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.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437911
--- Comment #3 from Lyubomir ---
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
https://bugs.kde.org/show_bug.cgi?id=437911
--- Comment #2 from Jan Grulich ---
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?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=437911
Jan Grulich changed:
What|Removed |Added
CC||jgrul...@redhat.com
--- Comment #1 from Jan
https://bugs.kde.org/show_bug.cgi?id=437911
Lyubomir changed:
What|Removed |Added
Summary|xdg-desktop-portal-kde and |xdg-desktop-portal-kde high
