After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 795188 - Broken font rendering since fcec6f721d5254b9010814023f98f541ca798b02
Broken font rendering since fcec6f721d5254b9010814023f98f541ca798b02
Product: pango
Classification: Platform
Component: coretext
Other Mac OS
: Normal major
: ---
Assigned To: gtk-quartz maintainers
Depends on:
Reported: 2018-04-12 07:44 UTC by hrubymar10
Modified: 2018-05-22 13:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description hrubymar10 2018-04-12 07:44:37 UTC
Tested OS: OS X 10.8 and newer
Problematic fonts:
Link to concrete font:

In our project, we are facing issue described here:

It is basically problem with font rendering with lato free fonts. All is working with Pango 1.40.1 but 1.40.2 have font rendering issues:

After some research we found commit, which causes issue:

If I take 1.40.1 release and apply patch from this commit I am able to reproduce font rendering issue.
Comment 1 Matthias Clasen 2018-04-12 12:51:17 UTC
thanks for tracking down the commit!
Comment 2 John Ralls 2018-04-12 13:58:36 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 787867 ***
Comment 3 hrubymar10 2018-04-15 21:13:07 UTC
John Ralls: I don't think that it is duplicate of bug 787867. Bug 787867 referring to other versions of Pango then mine... Can you look on it once more please?
Comment 4 John Ralls 2018-04-15 21:16:38 UTC
You're right. Sorry.
Comment 5 GNOME Infrastructure Team 2018-05-22 13:32:29 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: