Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. 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#58706 - [xterm] [noto-fonts-emoji] do not play together

Attached to Project: Arch Linux
Opened by Gaetan Bisson (vesath) - Wednesday, 23 May 2018, 20:23 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 14 December 2018, 19:26 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Andreas Radke (AndyRTR)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I'd like `xterm` to use the font from `noto-fonts-emoji`. However, running:

xterm -fa 'Noto Emoji'

Gives:

xterm: Selected font has no non-zero height for ISO-8859-1 encoding
xterm: Selected font has no non-zero width for ISO-8859-1 encoding
X Error of failed request: BadLength (poly request too large or internal Xlib length error)
Major opcode of failed request: 139 (RENDER)
Minor opcode of failed request: 20 (RenderAddGlyphs)
Serial number of failed request: 129
Current serial number in output stream: 177

And xterm immediately returns with status 1.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Friday, 14 December 2018, 19:26 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Wednesday, 23 May 2018, 20:30 GMT
Running `xterm -fd 'Noto Emoji'` works (no error) but the more complete `xterm -fa 'Noto Sans Mono' -fd 'Noto Color Emoji'` fails exactly as reported above.
Comment by Antonio Rojas (arojas) - Friday, 15 June 2018, 10:43 GMT
Works for me FWIW. Anyway, noto-fonts-emoji is simply installing the upstream provided ttf, so I doubt there's a packaging issue here, at least from the noto-fonts-emoji side.
Comment by Thomas Dickey (dickey) - Friday, 14 December 2018, 09:13 GMT
I noticed this earlier: it's a problem introduced into fontconfig a few years ago
instead of solving the actual problem (see fontconfig-bugs #87122)
I'll add a workaround in xterm.

Loading...