Bug 472695 - exa-master-upgrade breaks glyph rendering with OLPC XO [NEEDINFO]
exa-master-upgrade breaks glyph rendering with OLPC XO
Product: Fedora
Classification: Fedora
Component: xorg-x11-server (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
: Triaged
Depends On:
Blocks: FedoraOnXO
  Show dependency treegraph
Reported: 2008-11-23 12:32 EST by Daniel Drake
Modified: 2009-12-18 01:55 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 01:55:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
mcepl: needinfo? (dsd)

Attachments (Terms of Use)

  None (edit)
Description Daniel Drake 2008-11-23 12:32:28 EST
xorg-x11-server-1.5.3-5.fc10 includes xserver-1.5.2-exa-master-upgrade.patch which breaks text rendering on the OLPC XO.

It looks like this: http://dev.laptop.org/~dsd/20080822/text-not-ok.png

Removing that patch, plus the following which depend on it, solves the problem

We became aware of this problem in the 1.4.99 series when I discovered that the equivalent version of this patch fixed a different rendering bug for us, but broke glyph rendering in the fashion described here. The xserver developers confirmed that there is a known glyph truncation bug in master, and helped us find the exact part of this big patch which fixed our other problem.

But now that this patch is included in F10 and we have upgraded, the text rendering bug returns.
Comment 1 Matěj Cepl 2008-11-24 05:56:25 EST
Anything interesting in /var/log/Xorg.0.log?
Comment 2 Bug Zapper 2008-11-26 00:49:34 EST
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:
Comment 3 Peter Robinson 2009-02-02 15:41:20 EST
Daniel is this still an issue?
Comment 4 Matěj Cepl 2009-05-18 08:00:02 EDT
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Comment 5 Bug Zapper 2009-11-18 03:56:36 EST
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: 
Comment 6 Bug Zapper 2009-12-18 01:55:43 EST
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.

Note You need to log in before you can comment on or make changes to this bug.