I run two monitors in zaphod mode. The left one is rotated.
Acrobat reader shows artefacts along the TOC bar typically when I switch workspaces several times. A photo is attached.
It was not possible to take a screenshot directly as the artefacts vanished on the dump. Also, as I move the mouse pointer to the other screen, the artefacts vanish immediately.
The IGP is a Q965.
Thanks for your excellent work!
Created attachment 72997 [details]
artefacts acrobat rotated display
The artefacts are not present when I start Acrobat on the other screen with normal orientation.
This issue is not reproducable with xrandr/xinerama.
I just realised the description is not correct.
The artefacts do not vanish due to the pointer crossing the screen.
They vanish when the pointer triggers the focus of any other window on whatever screen.
Building the driver from git didn't improve the situation.
I suspect it is akin to bug #55500. Can you describe how you configure your zaphod displays so I can try and replicate your setup?
Created attachment 73009 [details]
The window manager is "awesome wm (3.4.13)".
Acrobat Reader is version 9.5.1
Take for example this document and open the bookmark panel:
I don't know how to reproduce the issue with other window managers but I can trigger the artefacts by switching to another workspace and back.
If you need further information, let me know.
Thanks for looking into this!
Created attachment 73180 [details]
corrupted glyphs on rotated screen
I saw you added some patches and, thus, tried the current git version.
The artefacts are still there (I guess it's expected) but now there are additional glyph corruptions (see attachments). Again, they only appear on the rotated screen.
Are you aware of them or should I file a new bug report?
Created attachment 73181 [details]
MIME type corrected
[The artefacts are not caught by the screendump]
Created attachment 74167 [details]
artefacts acrobat rotated display [video]
I just gave the current git a try.
The glyph corruption I reported in #7 is gone.
However, the artefacts are not.
While I know that you have other priorities right now,
I just wanted to know if you could reproduce the problem.
For me it is easy to trigger the artefacts by changing size
of the bookmark bar (see attached video).
That video definitely looks like bug #55500. Looks like you have a situation where it consistently occurs. :(
*** This bug has been marked as a duplicate of bug 55500 ***
I just did a bisection and came up with this commit:
Author: Chris Wilson <firstname.lastname@example.org>
Date: Fri Nov 30 12:17:25 2012 +0000
sna: Unify gen4 acceleration again
After disabling render-to-Y, 965g seems just as happy with the new code
paths as g4x.
Signed-off-by: Chris Wilson <email@example.com>
Judging from the date of the bisected commit, it does not *seem* to be a duplicate of #55500.
Yes, it is. It is exactly the failure of the GPU in handling VUE that is causing it to generate spurious fragments for the pixel shader. That is the underlying gen4 bug that is behind this and bug 55500.