FS#48300 - [freetype2] version 2.6.3 breaks when rendering Font Awesome
Attached to Project:
Arch Linux
Opened by Jack O'Connor (oconnor663) - Monday, 22 February 2016, 16:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 05 July 2016, 19:12 GMT
Opened by Jack O'Connor (oconnor663) - Monday, 22 February 2016, 16:28 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 05 July 2016, 19:12 GMT
|
Details
https://github.com/keybase/client/issues/2024
https://github.com/atom/electron/issues/4513 https://github.com/atom/atom/issues/10918 (with stacktrace) Launching the atom editor is the easiest way to repro this bug, though some users in the Keybase issue above reported that they were still able to use atom despite reproing the bug with Keybase. I'm trying to figure out whether that could be a difference between the `atom-editor` and `atom-editor-bin` packages. Downgrading freetype2 to version 2.6.2 fixes the issue. |
This task depends upon
Closed by Jan Alexander Steffens (heftig)
Tuesday, 05 July 2016, 19:12 GMT
Reason for closing: Upstream
Additional comments about closing: Problem with atom.
Tuesday, 05 July 2016, 19:12 GMT
Reason for closing: Upstream
Additional comments about closing: Problem with atom.
Comment by
Jan Alexander Steffens (heftig) -
Monday, 22 February 2016, 16:54 GMT
Comment by
Jack O'Connor (oconnor663) -
Monday, 22 February 2016, 20:43 GMT
Comment by
Jack O'Connor (oconnor663) -
Monday, 22 February 2016, 20:52 GMT
Comment by
Jan Alexander Steffens (heftig) -
Tuesday, 05 July 2016, 19:11 GMT
Can you bisect FreeType?
If I did this right, it looks like it bisects to commit
24aa9c665e3a8bbfbc5ae016354ffba7a1377fd3, "[autofit] Rewrite
HarfBuzz interface to support character clusters."
Commented about that result here:
https://github.com/atom/electron/issues/4513#issuecomment-187375365
Is this fixed now? Electron should now ship a newer harfbuzz.