Created attachment 45695 [details]
Example of mangled text.
My card is an old Radeon 9200 (rv280).
Using debian stable, w/mesa 7.7.1, text in opengl applications renders properly, but mesa is very slow, so I decided to try out mesa 7.10 from debian testing.
With debian testing (mesa 7.10), and unstable (mesa 7.10.2), the text is completely mangled and unreadable.
I will attach a screenshot of an xbmc screen from my htpc that shows the mangled text. Other OpenGL apps behave the same way; all the text is completely unreadable, but everything else renders beautifully (and quickly!)
Running OpenGL applications with LIBGL_DEBUG=verbose yields no errors other than:
libGL: Can't open configuration file /etc/drirc: No such file or directory.
libGL: Can't open configuration file /home/htpc/.drirc: No such file or directory.
The relevant entries from my dpkg listing:
ii libgl1-mesa-dev 7.10.2-1 A free implementation of the OpenGL API -- GLX development files
ii libgl1-mesa-dri 7.10.2-1 A free implementation of the OpenGL API -- DRI modules
ii libgl1-mesa-glx 7.10.2-1 A free implementation of the OpenGL API -- GLX runtime
ii libglu1-mesa 7.10.2-1 The OpenGL utility library (GLU)
ii libglu1-mesa-dev 7.10.2-1 The OpenGL utility library -- development files
ii mesa-common-dev 7.10.2-1 Developer documentation for Mesa
ii mesa-utils 8.0.1-2 Miscellaneous Mesa GL utilities
Adding the option: Option NoAccel true to xorg.conf makes the text render properly in all versions of Mesa, but as you'd imagine, makes programs unusably slow.
Let me know if you require any other information from me.
Looks like bug 34280, which was recently fixed.
I think you may be right.
Apologies for the bug duplication; font rendering issues yields a problem in searches in that there's so many synonyms to search for, and finding the bug you speak of may prove difficult. (Do I search for distortion or mangled or unreadable or rendered incorrectly, or .. or .. or.. :)
I'll give #34280 a check out tomorrow and reopen if it's not fixed, but I highly suspect that not to be the case.
Thanks for your help.
*** This bug has been marked as a duplicate of bug 34280 ***