Summary: | Font glyphs corrupted/missing with EXA on R300 | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Joel Feiner <jafeiner> | ||||||||||||
Component: | Server/Acceleration/EXA | Assignee: | Xorg Project Team <xorg-team> | ||||||||||||
Status: | RESOLVED DUPLICATE | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||
Severity: | major | ||||||||||||||
Priority: | medium | CC: | s.tousignant | ||||||||||||
Version: | git | ||||||||||||||
Hardware: | x86 (IA32) | ||||||||||||||
OS: | Linux (All) | ||||||||||||||
Whiteboard: | |||||||||||||||
i915 platform: | i915 features: | ||||||||||||||
Attachments: |
|
Description
Joel Feiner
2008-10-11 11:01:58 UTC
Created attachment 19591 [details]
Missing glyphs in KDE 4 application
Created attachment 19592 [details]
Large funts with missing glyph parts (KDE 3 - KOffice)
Please attach (as opposed to paste) the full Xorg.0.log as well. Does it also happen without Option "AGPFastWrite" and/or "AccelDFS"? Created attachment 19593 [details]
xorg.conf
Any combination of options with EXA seems to produce the same behavior: messed up or missing glyphs. Granted, I haven't tried the full Cartesian product, but I did try what you suggested, and a few other things (like MigrationHeuristic) and I still get the same behavior. Only switching back to XAA fixes it. Created attachment 20097 [details]
x86_64 arch Xorg.conf with same trouble with kde
i have the exact same issue, here is the my xorg.conf with skype.
with radeonhd, the font are rendered correctly.
Created attachment 20098 [details]
my Xorg.0.log
(In reply to comment #6) > i have the exact same issue, here is the my xorg.conf with skype. Have you tried Option "AccelDFS" "off" and Option "RenderAccel" "off" ? > with radeonhd, the font are rendered correctly. Does it have the functionality corresponding to the above options enabled? turning the following option off made the trick to get the font back to normal. Option "RenderAccel" "off" The Other option had no effect at all. The latest git xserver seems to fix this issue. I'm guessing it's related to commit 21c116219cd5c6845a0955f2d88fdb5fab5c17cf which addresses something that sounds very similar to this. *** This bug has been marked as a duplicate of bug 18065 *** |
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.