FS#29949 - [chromium] ignores fonts.conf (and still shows horrible fringe)

Attached to Project: Arch Linux
Opened by Carlos (memeplex) - Saturday, 19 May 2012, 18:09 GMT
Last edited by Evangelos Foutras (foutrelis) - Saturday, 19 May 2012, 19:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Evangelos Foutras (foutrelis)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

chromium 19.0.1084.46-2 is completely ignoring .fonts.conf (and Xft resources). For example, I've disabled antialiasing and every other app except for chromium shows jagged poor aliased fonts (as expected).

Also, the color fringe in chromium is intolerable (this was reported previously). Take a look at the attached screenshot comparing firefox (right) vs chromium (left). The font settings in both cases are:


<edit mode="assign" name="antialias"> <bool>true</bool> </edit>
<edit mode="assign" name="hinting"> <bool>true</bool> </edit>
<edit mode="assign" name="autohint"> <bool>false</bool> </edit>
<edit mode="assign" name="hintstyle"> <const>hintfull</const> </edit>
<edit mode="assign" name="rgba"> <const>rgb</const> </edit>
<edit mode="assign" name="lcdfilter"> <const>lcdlegacy</const> </edit>


Of course, chromium ignores them.

Additional info:
* package version(s) 19.0.1084.46-2


Steps to reproduce:
* modify ~/.fonts.conf
* run chromium
* nothing changed
* also: look at the fringe
   2012-05-19-150610_789x426_scr... (41.7 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Saturday, 19 May 2012, 19:23 GMT
Reason for closing:  Upstream
Additional comments about closing:  http://crbug.com/29871
Comment by Carlos (memeplex) - Saturday, 19 May 2012, 18:46 GMT
Sorry I didn't realize that chromium kept running at background after I quitted (maybe a new feature). So I wasn't really restarting it. .fonts.conf is indeed honoured. The fringe issue remains, so feel free to close this task and I will file another one specifically for that matter.
Comment by Carlos (memeplex) - Saturday, 19 May 2012, 18:50 GMT
Looks like if chromium is using its own lcdfilter and ignoring the one configured at fonts.conf. lcdlegacy, lcddefault and lcdnone all look the same (now really restarting :))
Comment by Evangelos Foutras (foutrelis) - Saturday, 19 May 2012, 19:03 GMT
You will probably have to file a bug report upstream [1] about the remaining
issue. I don't think I can help much, since it most likely isn't a packaging
problem. :)

[1] http://code.google.com/p/chromium/issues/list
Comment by Carlos (memeplex) - Saturday, 19 May 2012, 19:12 GMT
Done

https://code.google.com/p/chromium/issues/detail?id=128877&thanks=128877&ts=1337454749
Comment by Evangelos Foutras (foutrelis) - Saturday, 19 May 2012, 19:15 GMT
Found another report of what appears to be the same issue:

http://code.google.com/p/chromium/issues/detail?id=29871

I'm going to close this report; please follow the upstream one(s). :)

Loading...