Red Hat Bugzilla – Bug 486891
Corrupted font rendering on Radeon Mobility 9000
Last modified: 2009-11-09 19:06:26 EST
Created attachment 332885 [details]
Corrupted font rendering
Description of problem:
Text sometimes shows up with random dots or lines in it, especially in Firefox, on a Radeon Mobility 9000 chipset (Compaq Presario X1000 laptop). See attached screenshot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. View pages in Firefox
Text has random dots or lines in it
Proper text rendering
-Setting Option "RenderAccel" "no" in xorg.conf works around the problem.
-I tested latest Xorg git a while ago and this problem did not seem to occur in that version. The Xorg driver ABI version has changed from the F10 Xorg version, though.
-I originally mentioned this under bug 444890 as it seemed to be a similar problem, however that one was marked as supposedly fixed. This particular problem is not fixed.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf, if available) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 333581 [details]
Xorg log file
This is my Xorg.0.log file. The problem occurs with no xorg.conf file (all default settings).
I think I see something similar on my wife's computer, except it happens without regards whether I use nomodeset or not (and not 100% reproducable, just happens sometimes).
Screenshot of the corruption is attachment 342608 [details]
/var/log/Xorg.0.log is attachment 342609 [details]
/var/log/dmesg is attachment 342610 [details]
/var/log/messages attachment 342611 [details]
/etc/X11/xorg.conf (quite minimal) is attachment 342613 [details]
This bug no longer seems to occur in Fedora 11.
Marking as fixed.