Every time I reboot, I have to kill kmix as it is using 50% of the available processing power. This usually translate to an app using 100% on one core.

Has anyone else seen this behaviour?

not seen here, maybe rm your kdemix* config files?

I can't reproduce myself.

Have exactly the same problem. Oceanwatcher, did you find a solution?

I had an issue similar to this at one point. It was caused by a corrupt KMix profile. Try running the following:

Code: Select all

killall -9 kmix
rm -rf $(kde4-config --localprefix)/share/apps/kmix/
rm -f $(kde4-config --localprefix)/share/config/kmix*
kmix &

Thanks, bcooksley.

Seems that it helped. Will report if reoccurs again after restart

That is a very interesting cure. Although I am running Kubuntu, I took a chance that it would work for me. When issuing the last command I get this:

Code: Select all

svein@Aslan:~$ kmix &
[1] 2732
svein@Aslan:~$ QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/svein/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon
kmix(2733) sink_input_cb: Ignoring sink-input due to it being designated as an event and thus handled by the Event slider
QSystemTrayIcon::setVisible: No Icon set
kmix(2733) sink_input_cb: Ignoring sink-input due to it being designated as an event and thus handled by the Event slider

I will keep an eye on the temperature and see if it runs wild again.

Thank you for the fix!

The problem has not returned after the fix. Thank you very much!

Actually, it does return. Every two weeks for me. Applying the above solution puts it to sleep for two weeks again.

Please open a bug at bugs.kde.org the next time it happens, enclosing the broken files so it can get fixed for good.