Version: unspecified (using KDE 4.6.0) OS: Linux After starting 'kdesu konsole' third copy of dbus-daemon process starts (belongs to root, over two belongs to my user and 'messagebus') After using any command in root konsole dbus-daemon (root copy) takes 4% of CPU (before it was no digits at all). Common CPU usage becomes 70% (KSysGuard info) - before it was just 10%. I really don't know where over 60% comes to, because there is no processes with such CPU usage After exiting root konsole 'dbus-daemon' is still running with 4% CPU. After killing it common CPU usage become normal, but of course normal work with CDs or flash-drives becomes impossible I'm sorry if my English is not clear. I can give additional information if needed. Reproducible: Always Steps to Reproduce: 1. Start 'kdesu konsole' 2. Enter any command in terminal (exit is possible too) If close opened konsole as a window before step 2, then everything works fine and CPU usage remains normal Actual Results: High CPU usage, helps only reentering session Expected Results: Normal CPU usage Distro: Gentoo x86-64 Intel Core 2 Duo T6600 2.20GHz 4 GB RAM Also I know that such bug has other guy with different distro and KDE version (Debian Squeeze, KDE-4.4.5, xorg-server-1.7.7). Here is his post in russian forum - http://www.linux.org.ru/jump-message.jsp?msgid=5972028&cid=5972519
confirmed the behavior (though only once konsole exited, not when running commands in it): dbus-daemon eats some cpu, rest is burned in the kernel, probably playing message ping-pong with something. i'm not confirming this as a kde bug yet - it may a bug in dbus-daemon (or even the kernel). somebody with the inclination should attach strace to the amok running dbus-daemon and see where it loops. i can't reproduce that right now, as konsole now refuses to run from kdesu after i killed the offending process.
Reproduced this and have 3% CPU load on dbus-daemon's root copy process. Using KDE 4.6.1 Distro: ArchLinux Core 2 Duo T5600 1.83Ghz 2GB RAM
Created attachment 58739 [details] strace of dbus-daemon here's the strace from the dbus-daemon. i think it operates normally. the thing that goes wrong is knotify hammering it really hard. the unaccounted for cpu time comes from processes which are started and exit so fast that ps/top are not able to display them.
*** This bug has been confirmed by popular vote. ***
> After starting 'kdesu konsole' third copy of dbus-daemon process starts > (belongs to root, over two belongs to my user and 'messagebus') This happens with any KDE app, started with root privileges, for example kate. Also this starts kded4 process with root privileges, which I have to kill because it doesn't exit when I close that program, launched by kdesudo. But this happens once. If I launch kdesudo kate again after killing root kded4, new root kded4 process doesn't start anymore (need restart KDE session to happen it again).
Have 5% CPU load by dbus-daemon after trying to reproduce the issue. KDE 4.6.2, Debian unstable Core2 Duo @ 3.2GHz
I failed to reproduce the reported problem using KDE SC 4.8 beta1. No High CPU usage is observed afterwards.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.
Tested command /usr/lib/x86_64-linux-gnu/libexec/kf5/kdesu krusader & Looks OK.
Upd: System: Neon 20.04 Plasma version: 5.21.3 KDE Frameworks version: 5.80.0 Qt version: 5.12.2