Bug 825487

Summary: enlarging xterm while midnight commander is running leads to broken geometry after closing mc
Product: [openSUSE] openSUSE 12.3 Reporter: Thomas Hänig <haenig>
Component: X11 ApplicationsAssignee: Marcus Meissner <meissner>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: meissner
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 12.3   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Thomas Hänig 2013-06-18 06:19:43 UTC 
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0

when opening a local xterm (XFCE) starting midnight commander (mc) and after this resizing the xterm's window (increase width and height) and after this exit mc leads to e.g.:

thomas@thomas:~> set | grep LINES  
LINES=24

thomas@thomas:~> set | grep COLUMNS
COLUMNS=80

thomas@thomas:~> stty -a | grep speed
speed 38400 baud; rows 46; columns 134; line = 0;

resulting in garbled commandlines if prompt+command are actually longer than the value of $COLUMNS

=> xterm still believes to have it's former size

if I then resize the xterm again, everything is back to normal.

Reproducible: Always

Steps to Reproduce:
1. open xterm
2. launch mc
3. resize window (increase width and height)
4. exit mc
5. type a large command line
Actual Results:  
commandline is "warped" after $COLUMNS characters somehow onto the previous(!) line(s) or onto itself

Expected Results:  
commandline should wrap only at the right border of the xterm and only onto the following line(s)

thomas@thomas:~> cat /etc/issue
Welcome to openSUSE 12.3 "Dartmouth" - Kernel \r (\l).

thomas@thomas:~> rpm -qf /usr/bin/mc
mc-4.8.1.4-2.1.2.x86_64

homas@thomas:~> ldd /usr/bin/mc
        libslang.so.2 => /usr/lib64/libslang.so.2 (0x00007f45b6eaf000)

thomas@thomas:~> rpm -qf /usr/lib64/libslang.so.2
libslang2-2.2.4-4.1.1.x86_64
Comment 1 Marcus Meissner 2013-07-12 08:53:07 UTC 
lets track this in bug 828877

*** This bug has been marked as a duplicate of bug 828877 ***