Bug 583567 - After 30 seconds of inactivity, Xorg uses 100% cpu
Summary: After 30 seconds of inactivity, Xorg uses 100% cpu
Status: RESOLVED DUPLICATE of bug 584919
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: X.Org (show other bugs)
Version: Final
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Forgotten User Wum0mkMcd8
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-26 09:18 UTC by Ulrich Derenthal
Modified: 2010-03-05 07:46 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Derenthal 2010-02-26 09:18:30 UTC
I upgraded to KDE 4.4.0 using the packages from:

http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openSUSE_11.2/

Since then, I notice the following behaviour:

When I use my KDE desktop, the CPU usage is very low (a few percent).

When I don't use it (don't move the mouse and so on), the CPU usage stays low for exactly 30 seconds. Afterwards, "top" shows me that the Xorg process uses 100% of one of my CPUs (Thinkpad T60 with Intel Core 2 Duo). "top" tells me typically:

Cpu(s):  18.0%us, 35.0%sy, ...

Once I move the mouse again, CPU usage goes down to almost zero again. Doing nothing for 30 seconds again, CPU usage goes up again.
Comment 1 Dimitar Pashov 2010-02-26 16:36:36 UTC
I had the same issue when started using the 4.4 branch a few months ago. This bug really makes kde 4.4 unusable. It was frying my laptop.
Fortunately I figured out some temporary fix which you might want to try until the issue is fixed.

Go to the "Power Management" configuration applet/KDE Control Module. It has a battery on it and is usually found somewhere in the lower right corner. Click on the wrench and then on "Edit Profiles". Disable the "Dim display when idle for more than ..." field on each profile. You may also need to say "Do Nothing" to the "When the system is idle for more than ..." field on each profile.

I remember I carried some experiments with different times and found that X starts using 100% cpu at exactly half of the value of one of the two options I mentioned above. I don't remember which one now.

Good luck.
Comment 2 Stefan Dirsch 2010-03-05 07:46:12 UTC
dup

*** This bug has been marked as a duplicate of bug 584919 ***