Bug 561809

Summary: [abrt] crash in xterm-253-1.fc12
Product: [Fedora] Fedora Reporter: matti aarnio <matti.aarnio>
Component: xtermAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dickey, mlichvar, pertusus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:e689c9dfc0657c10c579993f0cf0aba88f73eb77
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-26 09:39:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description matti aarnio 2010-02-04 12:00:01 UTC 
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
Comment 1 matti aarnio 2010-02-04 12:00:04 UTC 
Created attachment 388770 [details]
File: backtrace
Comment 2 Thomas E. Dickey 2010-02-05 01:46:02 UTC 
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...
Comment 3 Thomas E. Dickey 2010-03-17 09:23:34 UTC 
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).
Comment 4 Miroslav Lichvar 2010-03-17 10:50:19 UTC 
Can you please verify the problem is fixed in xterm-256? (available in updates)
Comment 5 matti aarnio 2010-03-17 13:59:49 UTC 
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.
Comment 6 matti aarnio 2010-07-26 09:39:04 UTC 
The problem has not re-appeared.