Bug 999143 - fuzzy fonts after upgrading to rawhide
Summary: fuzzy fonts after upgrading to rawhide
Keywords:
Status: CLOSED DUPLICATE of bug 995643
Alias: None
Product: Fedora
Classification: Fedora
Component: fontconfig
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-20 19:41 UTC by Elad Alfassa
Modified: 2013-09-02 03:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-02 03:47:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Elad Alfassa 2013-08-20 19:41:37 UTC 
Description of problem:
http://i.imgur.com/yx1n4iv.png
Almost all fonts are fuzzy, apart from text in xchat scrollback box, Gnome Web (webkitgtk) and gnome-terminal.

This happened after I upgraded to rawhide.

If this is the wrong component please direct me to the correct one. Thanks.
Comment 1 Elad Alfassa 2013-08-20 22:29:13 UTC 
Further debugging suggests that it's cantarell specific, and downgrading fontconfig, pixman, cairo, and cantarell didn't help fix the problem.
Comment 2 Akira TAGOH 2013-08-21 02:59:46 UTC 
Are you talking about antialiasing?

How does it look like on f19 say?

How did you estimate it is cantarell specific? even though you said downgrading cantarell didn't help??
Comment 3 Elad Alfassa 2013-08-21 08:08:30 UTC 
I don't know if it's related to antialiasing. In f19, fonts look sharper. I know it's Cantarell specific because all other fonts look sharp, but only Cantarell looks fuzzy. If I change the hinting settings to "Slight", Cantarell looks sharp again but all other fonts look fuzzy.
Comment 4 sangu 2013-08-31 02:42:49 UTC 
Please see attachment 785048 [details] in bug 995643

After updating to FreeType 2.5.0, this issue happens.
Comment 5 Akira TAGOH 2013-09-02 03:47:59 UTC 

*** This bug has been marked as a duplicate of bug 995643 ***
Note You need to log in before you can comment on or make changes to this bug.