For me it is kacpid that is a runaway using 95% of a cpu and kacpi_notify uses only 5%. It seems to happen even if I don't run anything CPU intensive--just loggign in to KDE starts it. I guess I should try logging in to a console and see what happens.
For me it is kacpid that is a runaway using 95% of a cpu and kacpi_notify uses only 5%. It seems to happen even if I don't run anything CPU intensive--just loggign in to KDE starts it. I guess I should try logging in to a console and see what happens.