ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font

Status changed to 'Confirmed' because the bug affects multiple users.

That's what it seems like in firefox

This bug affects multiple users, but why ubuntu do not upgrade freetype to 2.9.x?

This is the upstream issue:

https://savannah.nongnu.org/bugs/?52613

I reported this bug about 1 year ago. The bug is introduced in

[base] Don't zero out allocated memory twice (#51816).
https://savannah.nongnu.org/bugs/?51816
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=bd28952e23bcd268a623ea5202e1cde4a92defe4

And fixed in:

Fix access to uninitalized memory (#52613).
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=e1090c608b72dcfc1899c33974acd056e120aa53

[base] Fix bitmap emboldening.
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=3b88576ba0807f5203310c22d5dbfff803c4abd9

To fix this problem, there are two ways:
(1) revert changes bd28952e
(2) merge e1090c60 and 3b88576b to current code base

I suggest (1) because it's simpler.

This is the patch that can directly put to "debian/patches-freetype" folder.

The attachment "fix_bitmap_emboldening.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

The new freetype version is in Ubuntu now, https://launchpad.net/ubuntu/+source/freetype/2.9.1-3

That doesn't resolve the issue in the stable series though. There has been only one report of the problem so far and little activity which suggests the issue is not impacting/annoying lot of users so probably a low priority one (are bitmap fonts commonly used? the upstream test case involves changing firefox configs to force the use of a specific fonts which doesn't sound like something users would usually do). Would still be nice to get fixed though so maybe a candidate to include with other fixes if a SRU is done to the LTS

Unsubscribing the Ubuntu Sponsors Team as there is nothing to sponsor.

Additionally, if you would like this to be in a stable release, the bug description must follow the template, which can be found here: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

As Sebastien notes though, as this is fairly low-priority, it will likely be included with other fixes.

Thanks!

Status changed to 'Confirmed' because the bug affects multiple users.

Fix not fix the problem in LTS version. I have installed 2.8.1-2ubuntu2 version and i have same problems. (Ubuntu 18.04)

xenial version working fine.