Package: stterm
Version: 0.8.1-2
Severity: important
Steps to reproduce:
1. Launch st with the DejaVu Sans Mono font:
st -f "DejaVu Sans Mono-10"
2. Run the following command:
printf '\xf0\x9f\x9b\x91\n'
Expected result:
- st displays U+1F6D1 OCTAGONAL SIGN, or some kind of unknown character
glyph, or maybe even just a blank space.
Actual result:
- st crashes, printing an error:
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: 949
Current serial number in output stream: 985
Note that with st's compiled-in default font, whatever it is, it displays a
blank space of the appropriate size instead of crashing. I discovered this
crash with Noto Sans Mono from the fonts-noto-core package, but I was able
to reproduce it with the much more widely available DejaVu Sans Mono.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.18.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8),
LANGUAGE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages stterm depends on:
ii libc6 2.28-5
ii libfontconfig1 2.13.1-2
ii libfreetype6 2.9.1-3
ii libx11-6 2:1.6.7-1
ii libxft2 2.3.2-2
ii ncurses-term 6.1+20181013-1
stterm recommends no packages.
stterm suggests no packages.
-- no debconf information
