Hi all, I'm newly using a rotated screen setup and see some misrenderings in both GTK and Qt applications that I was not able to dump with a frame grabber. This does _not_ occur on non-rotated setups, i.e. `xrandr --orientation normal`. I tried to bisect the issue and this happens with xf86-video-intel from git down to 2.10.0. Below that my compilation ended in dependency hell. --- System information: Linux 2.6.34 x86_64 intel i965 [git,2.10.0] xorg-server-1.8.1
Created attachment 36312 [details] artefacts on drop-down menue [firefox]
Created attachment 36313 [details] anther one, looking slightly different [firefox]
Created attachment 36314 [details] similar thing in Mathematica 7
Created attachment 36315 [details] debris after closing a drop-down menu
The meat of this bug is fixed by Chris' latest xf86-video-intel and libdrm commits [22/06/2010]. In particular these symptoms are gone now (for me): https://bugs.freedesktop.org/attachment.cgi?id=36313 https://bugs.freedesktop.org/attachment.cgi?id=36314 Still, I notice flickering [like tearing] (on rotated screen setups) when I move over menu items in drop-down menues - e.g. firefox (3.6.3). Hard to explain, but it looks like the highlighted section (mouse hover) is drawn not at once immediately but in fragments of contiguous rectangles (tiling?). Those are drawn with a slight delay which make them flickering. Strange enough, this also happens for my machine at home [r770] and rotated setup, so I'm not sure if this is a driver specific thing or an architectural shortcoming. So unless you want to elaborate on this further, consider this bug fixed. Thanks again, Chris!
Till, thanks for testing and reporting! The tearing effect I think is due (in part at least) to a miscalculation of the damaged region by the xserver, hence why it affects more than just intel drivers. [Of course, we don't rule out the possibility of there being additional bugs in our driver either...] For the damage, there has been some discussion, so we can reasonably expect the xserver to be shortly fixed. I'll close this bug in the hope that what I've just said holds true! :)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.