I don't know why this bug has been marked as invalid. Every screen
change triggers full screen XDamage event This is exactly what happens
and it didn't used to be this way. I run software that depends on damage
events and it has now ground to a halt. Yes, a damage event doesn't mean
that every
Hi there, reading the comments and having issues myself that seem
similar to this bug, I tried enabling the 'Show Repaint' plugin.
I soon as I activate it, my whole screen is constantly blinking: full
screen receives a pink overlay then some small area receives the pink
overlay once out of three
Vincent,
This bug has been found to be invalid as discussed above. That is still
true unless your full screen blinks constantly. If the full screen is
pink or coloured then that is not a problem. That's normal for Show
Repaint. It has to be /changing/ colour to indicate redraws.
First thing to
I can't see any bug in your test program right now. But I also can't
explain it.
If the root window was constantly getting damaged though, Show Repaint
would be flashing the whole screen and Compiz' CPU would be higher.
I see two possible explanations:
1. A bug in your program (which I can't
On Fri, Jan 18, 2013 at 7:50 AM, Launchpad Bug Tracker
1100...@bugs.launchpad.net wrote:
You have been subscribed to a public bug:
STR:
1. Compile and run the attached code - http://paste.ubuntu.com/1538829/
dumping the output to a file
2. Do something, open applications, open Dash, etc
To clarify some important things:
XDamage on the root window != screen redraws, especially with hardware overlays
XDamage on the root window != compiz damage. Its actually representative of
what's changed as a result of libGL doing a buffer swap
Composite and OpenGL being implicitly loaded when
Cool, thanks Sam
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1100456
Title:
Every screen change triggers full screen XDamage event
To manage notifications about this bug go to:
