Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a problem, that has only started recently, where occasionally, kicker will start to use 100% cpu. I can see this, as I run KSim, showing the cpu usage, and then when it's starts maxing out on one cpu, I'll run top. BTW This is a dual cpu setup.
I've never noticed it happen when I can see the desktop, and it's active. It's always when I come out of a screen save.
Is there any way to see what's causing kicker to "go crazy", or any way to stop it.
I've tried killing it, and this works, although I then lose the Task Bar, which makes the system kinda difficult to use, so I usually just restart X/KDE.
BTW This is with KDE 3.5.4 running on a Slack 11 system.
OK, this is still happening to me. But, I've narrowed it down a little.
It looks like it's KSim that *is* the problem. Once the CPU starts to "burn", if I remove the KSim from the KDE Panel, the CPU use drops. I can add KSim straight back in, and everything runs OK again. For a while LOL
Any ideas why KSim might suddenly, and randomly, start soaking up the CPU.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.