Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#50765 - [chromium] chromium ignoring FREETYPE_PROPERTIES

Attached to Project: Arch Linux
Opened by David Rosenstrauch (darose) - Tuesday, 13 September 2016, 14:44 GMT
Last edited by Evangelos Foutras (foutrelis) - Tuesday, 27 June 2017, 23:24 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 6
Private No

Details

As per the forum thread at https://bbs.archlinux.org/viewtopic.php?id=216988 since the freetype 2.7 upgrade chromium is displaying jagged fonts. (See attached screen shot.) The reason appears to be that it is ignoring the new FREETYPE_PROPERTIES environment variable. Any fix/workaround available? Is this an upstream bug?
   ChromiumJaggedFonts.png (270 KiB)
This task depends upon

Closed by  Evangelos Foutras (foutrelis)
Tuesday, 27 June 2017, 23:24 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems fixed in Chromium 59.
Comment by John (graysky) - Tuesday, 13 September 2016, 19:14 GMT
53.0.2785.113 has been released (our package has not yet updated to it though). When it does, do you still see this issue?
Comment by everytrash (everytrash) - Wednesday, 14 September 2016, 05:19 GMT
I have the sameproblem even with V53.

Thanks
Comment by John (graysky) - Wednesday, 14 September 2016, 12:17 GMT
@everytrash - Right, but 53.0.2785.113 has not yet been built for [community] yet. My point is that if there is an upstream bug, it may have been corrected in this release. Have you search upstream's bug tracker? I am running .113. Does the attached screenshot look bad to you?
   Screenshot_2016-09-14_08-17-0... (407.9 KiB)
Comment by John (graysky) - Wednesday, 14 September 2016, 12:23 GMT
Looks just a shitty on my ipad; I don't think this is a chromium bug at all. Have you tried it on another browser to confirm that it looks equally shitty?
   ipad.jpg (231.7 KiB)
Comment by David Rosenstrauch (darose) - Wednesday, 14 September 2016, 14:07 GMT
It's a chromium (and chrome?) bug. The browser didn't have jagged fonts prior to the freetype upgrade. And although other apps were suffering from jagged fonts post-upgrade, setting FREETYPE_PROPERTIES fixes it for all apps - except chromium.
Comment by John (graysky) - Wednesday, 14 September 2016, 16:17 GMT
Someone else should confirm. On my system rendering the nytimes.com looks identical on chromium, firefox, and on my ipad.
Comment by everytrash (everytrash) - Thursday, 15 September 2016, 06:34 GMT
@John
Thanks about the version note. Chromium ignores the FREETYPE_PROPERTIES setting. This is how it look's like:
   test.png (571.8 KiB)
Comment by Daniel Harrysson (nadley) - Thursday, 15 September 2016, 08:43 GMT
I can also confirm this. Fonts in chromium 53.0.2785.116-1 looks very bad when antialiasing is disabled. qutebrowser --backend webengine (which uses QtWebEngine) also looks bad. All other applications that I use (including firefox) looks good. I use FREETYPE_PROPERTIES="truetype:interpreter-version=35".
Comment by David Rosenstrauch (darose) - Thursday, 15 September 2016, 12:30 GMT
@graysky

In answer to your earlier question, I just upgraded chromium to 53.0.2785.116 but fonts are still broken.
Comment by David Rosenstrauch (darose) - Friday, 16 September 2016, 14:51 GMT
Does anyone know if there's an upstream bug report for this? If not, one of us should file one.
Comment by David Rosenstrauch (darose) - Friday, 23 September 2016, 20:42 GMT
FYI, there was a bug report filed upstream for this about a day ago:

https://bugs.chromium.org/p/chromium/issues/detail?id=649362
Comment by David Rosenstrauch (darose) - Wednesday, 25 January 2017, 16:02 GMT
Another related bug that was opened about this:

https://bugs.chromium.org/p/skia/issues/detail?id=6165

Loading...