Mageia forum

Hi,

I updated my computer today and since that moment, I have a kde4 process that take all the CPU.

Do you know why and what I can disable to stop that ?
(I tried the desktop effect but no changes... neither with logout or reboot).

Pierre

This is a known problem that is already discussed at the Mageia-dev-mailinglist.
There's no solution at the moment.

Stay cool and have a drink meanwhile ...

cheers,
Bernd

I experience the same issue. The process which eat all of one CPU's core is kded4. If you have a single core, it will take all the CPU.
This issue is currently debated on the mageia-dev ML, of which the archive can be found here: https://mageia.org/pipermail/mageia-dev ... 06176.html

For the moment, this command should fix it:

Code: Select all

kill -9 `pidof kded4`

Of course this is suboptimal because: kded4 will be dead (but my KDE seems to work fine without it at the moment) and you have to kill it again after each reboot. Hopefully this issue will be fixed soon.

This behavior has been recognized by KDE.
Probably an issue on ntrack, the "ntrack package might be broken".
Fix can be expected some time ahead.

Akien wrote:

Code: Select all

kill -9 `pidof kded4`

Of course this is suboptimal because: kded4 will be dead (but my KDE seems to work fine without it at the moment) and you have to kill it again after each reboot. Hopefully this issue will be fixed soon.

I did CTRL ESC and a term on the KDE 4 process for the same result.

Thanks
Pierre

BTW : With this version, desktop effect in opengl issue is resolved

hello

i had the same problem with kded4 process... i've found a solution on kubuntu forum that fixed it...

in "/usr/share/kde4/services/kded/networkstatus.desktop" at the end of file change "X-KDE-Kded-autoload=true" to "X-KDE-Kded-autoload=false"

The issue should be fixed by kdebase4-runtime-4.6.90-4.mga2, submitted by mikala 2 days ago, which adds a requires on ntrack.

the problem was resolved yesterday on my computer

Solved here as well in my Cauldron-environment.

I had this yesterday. Solved it by cleaning out all /tmp directories and ~/.cache, following a different forum post.