Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#61115 - [xterm] crashes with mutt
Attached to Project:
Arch Linux
Opened by Gaetan Bisson (vesath) - Monday, 17 December 2018, 22:22 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 19 December 2018, 05:16 GMT
Opened by Gaetan Bisson (vesath) - Monday, 17 December 2018, 22:22 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 19 December 2018, 05:16 GMT
|
DetailsRunning mutt on a certain mailbox inside xterm I get:
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) Serial number of failed request: 3647 Current serial number in output stream: 3695 The return code is 83. Narrowing down the exact cause of the crash is not straightforward but I'll try to bisect my mailbox's content to see what exactly is the problem. I can reproduce this bug with both xterm-337-1 from [extra] and xterm-339-1 from [testing]. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Wednesday, 19 December 2018, 05:16 GMT
Reason for closing: Fixed
Additional comments about closing: xterm-340-1 in [testing]
Wednesday, 19 December 2018, 05:16 GMT
Reason for closing: Fixed
Additional comments about closing: xterm-340-1 in [testing]
(Whether `Mono` resolves to Inconsolata, Nimbus or Menlo does not change anything.)
FS#58706- if not please get in contact with upstream.