Hello

Not sure if this is the best forum to ask this question.

This is more of a question than a problem - I usually have about 45 instances of akonadi_contact running.

Is this normal?

Thanks in advance

It doesn't seem normal, I have one instance only of my addressbook running. Can you try to see if it happens with a new user?

Thanks - I set up a new user and only the one instance is running now.

I guess the other user had got corrupted somehow. I may as well stick with the new one, eh.

I'll keep an eye on the new user and see if the same problem develops over the next few days, fingers crossed though!

I've rebooted twice since my new user and now have 3 instances of akonadi_contact running.

I think I get a new instance created each time I boot.

EDIT I don't need Akondai as I don't use KMail etc can I just disable it?

Akonadi is started by the Plasma Clocks unfortunately, and only starts on demand. It seems that the migrator is running every time you login. You can use the control panel accessible through "kcmshell4 akonadi" to remove these extra resources which are being added.

Thanks for that - I'll report this as a bug.

I notice I have a lot of duplicate processes now, although the akonadi_contact issue is resolved.

6 instances of nepmukservices
5 instances of agetty.
2 dbus-daemon
10 instances of kworker


..and others too.

IS this a KDE issue or an Arch issue?

If you logout do the instances persist? Haven't heard of kworker before....

bcooksley wrote:If you logout do the instances persist? Haven't heard of kworker before....

Yes - I just logged in after booting up and things are much the same.

The "nepomukservices" are likely actually "nepomukservicestub" processes, which each provide a different Nepomuk related service needed for it's operation.

"agetty" sounds like the getty program which would run on your virtual terminals.

"dbus-daemon" is probably being run once by your user, and once as a system-wide instance. If so, this is expected, as it creates the system wide and session buses seperately.

Can you try and see where "kworker" comes from... I don't have that process or binary on my system.