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. ** Bug watch added: Non-GNU Savannah Bug Tracker #52613 http://savannah.nongnu.org/bugs/?52613 ** Bug watch added: Non-GNU Savannah Bug Tracker #51816 http://savannah.nongnu.org/bugs/?51816 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769132 Title: ubuntu18.04's libfreetype6 2.8.1 has a bug of rendering bitmap font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1769132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
