abrt 1.0.4 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/bin/xterm component: xterm executable: /usr/bin/xterm kernel: 2.6.31.12-174.2.3.fc12.x86_64 package: xterm-253-1.fc12 rating: 4 reason: Process was terminated by signal 6 (Aborted) release: Fedora release 12 (Constantine) comment ----- See above. This probably does not happen, if xterm starts to UTF8 mode. Just necessitating mode change causes crash. How to reproduce ----- 1. Start xterm in non-UTF8 mode 2. output some UTF-8 characters on terminal, observe that they are line noise 3. turn on UTF-8 from control-Right-button menu 4. use program that causes terminal to flip on alternate screen (like "nano" editor) 5. exit that program -> xterm crashes
Created attachment 388770 [details] File: backtrace
It might be data-dependent, or resource-dependent. The resource-settings would help, particularly if it's easy for you to reproduce (making data less likely). (a quick check here doesn't break xterm #255, and I don't see that I'd touched this area). I'll check the backtrace and see if I can find the bug...
I was unable to trigger this bug, but it sounds like the same case as this: Patch #255 - 2010/1/21 + correct logic used to switch to alternate screen using FIFO-lines configuration (Debian #565772).
Can you please verify the problem is fixed in xterm-256? (available in updates)
My quick test shows UTF-8 being used everywhere even when I try to command other modes, which may mask the issue. Anyway closing the pico editor inside this xterm does not cause the xterm to crash anymore.
The problem has not re-appeared.