Red Hat Bugzilla – Bug 459859
[EXA] Font garbage and X display disorder
Last modified: 2013-01-09 23:46:52 EST
Description of problem:
With xorg-x11-server 220.127.116.116-9.fc10 fonts on many applications
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login to GNOME session (at this stage some fonts are already corrupted)
2. launch some applications
Screen shot will be attached below
Screen shot will be attached below
With 18.104.22.1686-5.fc10 I see no problem for fonts rendering.
I have another problem with xorg-x11-drv-i810-2.4.0-2.fc10 so currently
I use this xorg-x11-drv-i810 (bug already reported as bug 459777)
Created attachment 314855 [details]
screenshot of JD with 22.214.171.1246-9.fc10
Created attachment 314856 [details]
screenshot of JD with 126.96.36.1996-5.fc10 (this is clean)
Created attachment 314857 [details]
Created attachment 314858 [details]
Xorg.0.log (with xorg.conf)
Created attachment 314859 [details]
Xorg.0.log (with xorg.conf removed)
With xorg.conf removed, still fonts are corrupted.
xorg-x11-server-188.8.131.526-10.fc10 still has this issue.
With xorg-x11-server-Xorg-1.5.0-1.fc10 I don't see this issue.
With xorg-x11-server-Xorg-1.5.0-6.fc10.i386 fonts display is _terribly_ disturbed.
Created attachment 316514 [details]
JD screenshot with 1.5.0-6.fc10
Created attachment 316515 [details]
Quite possibly driver issues.
Still I observe this issue on:
With xorg-x11-server-Xorg-1.5.0-1.fc10 I don't see this issue
Rebasing to 1.5.1-6.fc10, disabling Patch102 and Patch104 works for me
When only Patch102 is disabled applying Patch104 hangs up (so I cannot
(In reply to comment #11)
> Quite possibly driver issues.
With xorg-x11-server-Xorg-1.5.2-4.fc10, when switching to vesa driver
I don't see this problem.
When using intel driver xorg-x11-drv-i810-2.4.2-12.fc10 I still
see this issue.
Created attachment 320427 [details]
Note that xorg.conf is completely removed.
Created attachment 321384 [details]
screenshot of JD
this issue got much more serious.
Not only glyphs display is broken, it frequently happens that
some part of X window display is out of sync.
screenshot of JD is attached.
Adding F10DesktopBlocker. Please triage.
Do you see this only in JD, or also in other applications?
(In reply to comment #18)
> Do you see this only in JD, or also in other applications?
Also in other applications (such as firefox, thunderbird and so on).
When I disable Patch102, 104, 105 things go much better
(I don't know the reason, however I tried to look diff between
my comment 7 and comment 8, and I found that between these
Patch102 seemd to have been added)
Presumably if you set AccelMethod to XAA, it works?
(In reply to comment #20)
> Presumably if you set AccelMethod to XAA, it works?
Actually it does work, with xorg.conf:
Option "AccelMethod" "XAA"
(currently this is all contents of xorg.conf),
Moving to target, we would not slip the release for this issue.
xorg-x11-server Fedora CVS F-10 HEAD
(1.5.3-2.fc10, however not be rebuilt on koji yet)
WORKS, perhaps related to bug 470638.
I would appreciate it if 1.5.3-2.fc10 is included in f10-final.
Created attachment 323335 [details]
screenshot of firefox with 1.5.3-2
(In reply to comment #23)
> xorg-x11-server Fedora CVS F-10 HEAD
> (1.5.3-2.fc10, however not be rebuilt on koji yet)
Sorry, it seems that I was telling a lie.
With 1.5.3-2.fc10, I see the problem (screenshot attached)
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 '10'.
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 10'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 10 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:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.