Created attachment 385861 [details] Dillo on startup without the workaround Description of problem: Text in some applications corrupted so that it is completely unreadable Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.7.4-1.fc12.i686 xorg-x11-drv-ati-6.13.0-0.20.20091221git4b05c47ac.fc12.i686 (all rpms up to date with yum update) How reproducible: Always Steps to Reproduce: 1. Boot with nomodeset 2. No xorg.conf, so default + autodetect options 3. On a ATI Technologies Inc Radeon RV100 QY start ooffice Actual results: Menu fonts are unreadable. Text of document is fine. Expected results: Fonts should be readable Additional info: 02:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE] (prog-if 00 [VGA controller]) Subsystem: Hightech Information System Ltd. Device 0f02 Flags: bus master, stepping, 66MHz, medium devsel, latency 32 Memory at e0000000 (32-bit, prefetchable) [size=128M] I/O ports at c000 [size=256] Memory at ed000000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at ec000000 [disabled] [size=128K] Capabilities: <access denied> Kernel modules: radeon, radeonfb Without nomodeset I am experiencing lock ups, which is clearly a separate problem. The nomodeset workaround was fine in Fedora 11. I experience the same problem with another program I wrote myself, which uses pango/gtk2 to display fonts. Some are fine, others are missing. Also with the dillo web browser the text on the web page appears fine, when the application is started, but if any exposure is generated, the part which is exposed is redrawn with the corrupted fonts. This seems to indicate that there is nothing wrong with the fonts themselves, as they are drawn correctly at first. There are no relevant messages in /var/log/messages. I tried creating an xorg.conf file and found that the option: Option "AccelMethod" "EXA" in the device section works around the bug.
Created attachment 385862 [details] Dillo after exposure event without the workaround
Created attachment 385863 [details] Xorg.0.log with XAA accelmethod
Created attachment 385864 [details] Xorg.0.log with EXA accelmethod (this one works) With no xorg.conf or with AccelMethod XAA the fonts are corrupt. With AccelMethod EXA, the bug is worked around.
I'm seeing this bug on an RV740 (HD 4770). All fonts except the document fonts in e.g. Chrome are corrupted. All the fonts in GDM are corrupted, for example. This only happens with kernel 2.6.33-0.26.rc6.git1.fc13.x86_64 and up; booting into an older kernel resolves the issue, independent of which version of the -ati driver is in use. My uneducated guess is that it's something in the kernel DRM, not the X stack.
Could we get /var/log/Xorg.0.log without any xorg.conf whatsoever (i.e., in configuration which doesn't work), please? Thank you
Created attachment 389916 [details] Xorg.0.log without any /etc/X11/xorg.conf (exhibits problem with fonts) As requested, the Xorg.0.log without any /etc/X11/xorg.conf. The result is the same as with the xorg.conf set to use XAA which I posted before. i.e. the fonts are corrupted.
Sean, I only have kernel 2.6.31.12-174.2.3.fc12.i686.PAE not 2.6.33 so that is not my problem, unless some bug was introduced earlier in the i686.PAE kernel and later in the x86_64 kernel.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.