SUMMARY Often when I start Plasma Wayland session there are few processes named xdg-desktop-portal-kde using a lot of CPU. Maybe because they fail to start properly? SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.2 KDE Frameworks Version: 5.71 Qt Version: 5.15.0 Is there a log I can provide next time it happens?
Try to kill them all and run one with: QT_LOGGING_RULES='xdp*.debug=true' /usr/libexec/xdg-desktop-portal-kde or wherever your xdg-desktop-portal-kde is located. Attach here the output please.
Same problem here. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.80 (compiled with kdesrc-build) KDE Frameworks Version: 5.72 Qt Version: 5.15.0 I killed all xdg* processes, but starting the new one succeded without a problem: $ QT_LOGGING_RULES='xdp*.debug=true' /usr/lib/xdg-desktop-portal-kde xdp-kde-wayland-integration: Egl initialization succeeded xdp-kde-wayland-integration: "EGL version: 1.5" xdp-kde: Desktop portal registered successfully xdp-kde-wayland-integration: Registry initialized xdp-kde-wayland-integration: Adding output: xdp-kde-wayland-integration: manufacturer: "CMN" xdp-kde-wayland-integration: model: "eDP-1-unknown" xdp-kde-wayland-integration: resolution: QSize(1920, 1080)
Well, I now built Plasma again, rebooted a few times and can't reproduce it with xdg processes anymore. kdeconnectd seems to sometimes still go rogue though.
This might be caused by drkonqi getting stuck when something crashes because since I uninstalled it I don't have this issue and It (dkonqi) was always running when this problem occured. Anyway, this bug is not caused by xdg-desktop-portal-kde so this issue can be closed now, ideally if someone else can confirm.
*** Bug 423513 has been marked as a duplicate of this bug. ***
(In reply to Jan Grulich from comment #1) > Try to kill them all and run one with: > QT_LOGGING_RULES='xdp*.debug=true' /usr/libexec/xdg-desktop-portal-kde > > or wherever your xdg-desktop-portal-kde is located. > > Attach here the output please. Not OP but, after killing it and starting it, it seems the thing was resolved
This is not an issue caused by xdg-desktop-portal-kde, but by drkonqi.