On Thu, Dec 13, 2018 at 02:11:28PM +0100, Vincent Lefevre wrote: > Package: xterm > Version: 338-1 > Severity: grave > Justification: renders package unusable > > After upgrading xterm to 338-1, I get X errors when using GNU screen: > > zira% xterm -e screen -r > /usr/bin/xterm: warning, error event received: > 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)
Perhaps it's a problem with the Xft improvements and a particular glyph for which Xft/freetype2/fontconfig breaks. The strace shows that xterm's opened a second font, and dies shortly after: 1281 openat(AT_FDCWD, "/usr/share/fonts/truetype/dejavu/DejaVuSansMono.ttf", O_RDONLY) = 5 1281 openat(AT_FDCWD, "/usr/share/fonts/truetype/noto/NotoColorEmoji.ttf", O_RDONLY) = 5 I haven't run into anything like this, of course, but with the font information and a (script) typescript to see what's sent to the screen, can probably see what's breaking. I could add a feature to tell xterm to not exit on (certain) errors if it's not actually an xterm bug. Seems it's not: https://groups.google.com/forum/#!topic/wmii/i92CyORGZQ0 https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1498269 https://github.com/cdown/clipmenu/issues/88 > Serial number of failed request: 1168 > Current serial number in output stream: 1200 > > This one is now always reproducible. > > I've attached a compressed strace output, if this can be helpful. -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature