Bug 182382 - xterm crashes with -cm option
Summary: xterm crashes with -cm option
Alias: None
Product: Fedora
Classification: Fedora
Component: xterm
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-02-22 03:57 UTC by Alan
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-08-17 15:53:12 UTC
Type: ---

Attachments (Terms of Use)

Description Alan 2006-02-22 03:57:21 UTC
Description of problem:
After upgrading my xterm rpm, "xterm -cm now" crashes 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install xterm-208-1.FC4 
2. xterm -cm
Actual results:
xterm crashes with the following output:
xterm:  warning, error event received:
X Error of failed request:  BadGC (invalid GC parameter)
  Major opcode of failed request:  65 (X_PolyLine)
  Resource id in failed request:  0x9feb650
  Serial number of failed request:  212
  Current serial number in output stream:  226

Expected results:
xterm runs with ANSI color sequences disabled as per the man page.

Additional info:
I've tried this on two seperate fc4 boxes with the same results.
downgrading to 207-2.FC4 fixes problem (problem introduced in newest version)

Comment 1 Jason Vas Dias 2006-02-22 16:48:07 UTC
Very strange - this is NOT happening at all on the two FC-4 machines I've tested -
'xterm -cm' works fine.
You are running the latest xorg-x11-6.8.2-37.FC4.49.2 release with
glibc-2.3.5-10.3 ?  GNOME or KDE window manager ? 
What architecture - i386 / x86_64 ? 

Please could you download and run this debugging version of xterm : 
Download and install the xterm-debug-208-1.DBG.i386.rpm if you are running on 
an ia32e platform, or download the xterm-debug-208-1.DBG.src.rpm and run
  # rpmbuild --rebuild xterm-debug-208-1.DBG.src.rpm
and install the resulting /usr/src/redhat/RPMS/${ARCH}/xterm-debug*.rpm.

This provides ONLY the /usr/bin/xterm-debug executable, and does not 
conflict with your existing xterm installation - it will tell us exactly
where  / why the error is occurring.

  # ulimit -c unlimited; xterm-debug -cm
will create the Trace-{parent,child}.out files in the current directory, and,
if any X error occurs, will create a core.$pid coredump file.
  Please tar up these files:
  # tar -cpf - Trace-{parent,child}.out core.* | gzip > xterm-debug.tar.gz
and send me (jvdias) the resulting xterm-debug.tar.gz file or
append it to this bug report - thank you!

Comment 2 Thomas E. Dickey 2006-02-22 17:30:03 UTC
I can reproduce this (at least once).  I'll take a look now and
give more information if it stays.

Comment 3 Thomas E. Dickey 2006-02-22 17:55:12 UTC
It's time-sensitive, but might be a variation of 178302.
In this case, the if-statement further down in set_cursor_gcs()
    } else
    if (cc != fg && cc != bg) {
        /* we have a colored cursor */
doesn't match the previous if-statement, which happens to check if the
window's been created.  If I change that to
    } else
    if (VWindow(screen) != 0 && (cc != bg)) {
        /* we have a colored cursor */
then the problem appears to go away.

Comment 4 Jason Vas Dias 2006-02-22 19:20:17 UTC
Aha! Thanks, Thomas - patch applied in xterm-208-2.FC4 and xterm-209-2(FC5) .

Please try out the xterm-208-2.FC4 RPMs (available shortly from FC-4 
Updates/Testing) and let me know if the problem is fixed - thanks!

Comment 5 Fedora Update System 2006-02-22 19:34:22 UTC
From User-Agent: XML-RPC

xterm-208-2.FC4 has been pushed for FC4, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Comment 6 Alan 2006-02-22 19:56:25 UTC
just tested 208-2.FC4, problem fixed.
thanks all

Comment 7 Thomas E. Dickey 2006-02-22 20:13:32 UTC
thanks for the verification - I'll have that fix in #210

Comment 8 Fedora Update System 2006-03-01 22:01:31 UTC
From User-Agent: XML-RPC

xterm-208-2.FC4 has been pushed for FC4, which should resolve this issue.  If these problems are still present in this version, then please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.