In Dapper Xorg is extremely Power Hungry

Bug #48587 reported by David Losada Gacio
8
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

For example:
In Dapper Xorg uses 3 times more processor power with Superkaramba:
With certain themes (those very big, I suppose) like sys_mon Xorg is so power hungry that the system is sluggish (e.g. when watching movie the image stops every 4 seconds for 0.5 seconds, dropping frames).
On breezy, same version of Superkaramba and sys_mon used 15% of CPU; now it uses 45-60%.
System spec: Athlong 64 3000+ 1GB Ram Nvidia 6200 256Mb DDR2 with Nvidia-glx driver (nv). DRI and GLX activated.

I have tested the live CD in another system (PIV 2400 512 Mb Ram) to verify the slowness, and the system peaks CPU use with every window movement.
Other bugs like #38131 and #1363 could be the related.

I think it could be due to the "virtual" transparence of this theme and his area over the desktop. I think this is not kde-related, as long as I had kde 3.5 on breezy.

I will summit xorg.conf and sys_mon if asked.

I'm sorry for my english, hello from Spain.

Revision history for this message
David Losada Gacio (losadaz) wrote : Cynapses Karamba

Theme for Superkaramba that makes the system almost unusable

Revision history for this message
David Losada Gacio (losadaz) wrote : Xorg config

The config file of Xorg.

Revision history for this message
David Losada Gacio (losadaz) wrote :

After a time I tested other themes for SuperKaramba, and those didn't had this problem. It must be a problem with superkaramba using some xorg functions included with dapper that are not optimized in the new version of Xorg (7.0), so the background is refreshed too many times... (is a thought)

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Not a Xorg bug.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Still an issue in Intrepid?

Changed in superkaramba:
status: New → Incomplete
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in kdeutils:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.