Why does kded4 hog one of my processors?

On this two-processor machine, running OpenSUSE 11,1 and KDE4.2, kded4 is
running persistently at 50% and as one processor is almost permanently at
100%, I assume kded4 is hogging that one.

On another (single-processor) machine running 11.1 and KDE4.1, kded and
kded4 are both at 0%.

Why is kded4 so greedy on this machine?


Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy

You need to see what process is eating up power. Two ways:

  • in Konsole, type ‘top’ (w/o quotes) and then [enter]
  • on the desktop Alt+F2, then click on ‘Show system activity’ (the 2nd button in the bar that appears)

There may be some indexing services in the background (Strigi, Beagle).

adrian-cozma wrote:

>
> You need to see what process is eating up power. Two ways:
>
> - in Konsole, type ‘top’ (w/o quotes) and then [enter]
> - on the desktop Alt+F2, then click on ‘Show system activity’ (the 2nd
> button in the bar that appears)
>
> There may be some indexing service in the background (Strigi, Beagle).
>
>

Thanks for introducing me to those commands but they only confirm what I’d
already seen in System Monitor, i.e, the process that’s hogging a processor
is kded4.

One bit of variety from hogging one processor: I’ve just seen it switch
processor to the other one - must have been getting bored and wanted a
change of scenery.


Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy

In the system monitor, kill the kded4 process. Log out and log back in.

Last week what you are describing happened to me, I killed the process logged out and logged back in and it hasn’t happened since.

I can’t promise it will work for you, but it worked for me, it’s worth a try.

brucecadieux wrote:

>
> In the system monitor, kill the kded4 process. Log out and log back in.
>
> Last week what you are describing happened to me, I killed the process
> logged out and logged back in and it hasn’t happened since.
>
> I can’t promise it will work for you, but it worked for me, it’s worth
> a try.
>
>

Thanks, that’s done the trick.


Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy

Just worked for me too.

Ghost in the machine?

sorry, couldn’t resist :stuck_out_tongue:

Make sure kio_http is not hogging that 50%, if so - you might have some plasmoids/applets that are bugging, for example there has been talk of that weather plasmoid from the community repo bugging hard.

I had the same issue, but my solution was to kill kded4, then restart it from the console using “kded4&”. After that, everything went on fine, no need to relogin.

I noticed that my kded4 starts chewing on the CPU when I change from my wireless connection back to my wired ethernet connection.