FS#6085 - display of 3D graphics is badly compromised after latest X update
Attached to Project:
Arch Linux
Opened by name withheld (Gullible Jones) - Tuesday, 26 December 2006, 16:24 GMT
Last edited by Jan de Groot (JGC) - Thursday, 31 May 2007, 23:48 GMT
Opened by name withheld (Gullible Jones) - Tuesday, 26 December 2006, 16:24 GMT
Last edited by Jan de Groot (JGC) - Thursday, 31 May 2007, 23:48 GMT
|
Details
OpenGL applications now have their graphics displaced from
where they ought to be. In addition, windows for OpenGL apps
leave trails , and the displaced 3D graphics obscure other
windows; the trails stick around even after the offending
application is closed. Here are three screenshots that show
what I'm talking about.
BZFlag showing displaced graphics: http://xs.to/xs.php?h=xs510&d=06522&f=Screenshot1.png glxgears showing displaced graphics: http://xs.to/xs.php?h=xs510&d=06522&f=Screenshot2.png glxgears after being dragged around the desktop: http://xs.to/xs.php?h=xs510&d=06522&f=Screenshot3.png No error messages in Xorg.0.log, or in console when running OpenGL apps. |
This task depends upon
b) doesn't happen
c) doesn't happen
this all on a nvidia card
Now my question: which driver, openchrome, unichrome or via? You never give such information when posting these bugs.
I think this, as well as #6060, is related with drivers for your VIA video.
What's odd about this is that there was no version change with the openchrome drivers, and they're affected too.
The latest Mesa changelog does mention some stuff about a new memory manager; as of now that's only for Intel drivers though, so I don't really see how it could mess up via/unichrome/openchrome.
(My best guess is that unichrome-dri doesn't like being built against the new version of mesa, or something along those lines.)
Do you still encounter the lockups with indirect rendering forced BTW?
I'll have to find out if anyone using Intel graphics is getting this stuff...
http://bbs.archlinux.org/viewtopic.php?id=32547
Updating the version in the repos to the current 6.5.3 should fix it.