Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 950255

Summary: xterm segfaults if you cat /var/log/boot.log
Product: Red Hat Enterprise Linux 6 Reporter: Schlake <wcolburn+bugzilla>
Component: xtermAssignee: Miroslav Lichvar <mlichvar>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4CC: cww, dickey, dkochuka, tpelka, wcolburn+bugzilla
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-28 22:14:40 UTC Type: Bug
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
this boot.log crashes an xterm
none
typescript of trying those rpms
none
output of xrdb -query command none

Description Schlake 2013-04-09 23:13:22 UTC
Description of problem:
xterm segfaults after catting /var/log/boot.log

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


How reproducible:
cat /var/log/boot.log then do something else


Steps to Reproduce:
1. cat /var/log/boot.log
2. dmesg
3.
  
Actual results:
Program received signal SIGABRT, Aborted.                                       
0x0000003643c328a5 in raise () from /lib64/libc.so.6                            
Missing separate debuginfos, use: debuginfo-install expat-2.0.1-11.el6_2.x86_64 fontconfig-2.8.0-3.el6.x86_64 freetype-2.3.11-14.el6_3.1.x86_64 glibc-2.12-1.107.el6.x86_64 libICE-1.0.6-1.el6.x86_64 libSM-1.2.1-2.el6.x86_64 libX11-1.5.0-4.el6.x86_64 libXau-1.0.6-4.el6.x86_64 libXaw-1.0.11-2.el6.x86_64 libXcursor-1.1.13-2.el6.x86_64 libXext-1.3.1-2.el6.x86_64 libXfixes-5.0-3.el6.x86_64 libXft-2.3.1-2.el6.x86_64 libXmu-1.1.1-2.el6.x86_64 libXpm-3.5.10-2.el6.x86_64 libXrender-0.9.7-2.el6.x86_64 libXt-1.1.3-1.el6.x86_64 libgcc-4.4.7-3.el6.x86_64 libutempter-1.1.5-4.1.el6.x86_64 libuuid-2.17.2-12.9.el6.x86_64 libxcb-1.8.1-1.el6.x86_64 ncurses-libs-5.7-3.20090208.el6.x86_64                                             
(gdb) where                                                                     
#0  0x0000003643c328a5 in raise () from /lib64/libc.so.6                        
#1  0x0000003643c34085 in abort () from /lib64/libc.so.6                        
#2  0x0000003643c707b7 in __libc_message () from /lib64/libc.so.6               
#3  0x0000003643c760e6 in malloc_printerr () from /lib64/libc.so.6              
#4  0x0000003643c7bae7 in _int_realloc () from /lib64/libc.so.6                 
#5  0x0000003643c7bca5 in realloc () from /lib64/libc.so.6                      
#6  0x000000000042f74f in ScrnPointers (screen=0x69c278, len=1)                 
    at ./screen.c:996                                                           
#7  0x0000000000430253 in ScrnClearLines (xw=0x69c100, sb=0x6d3290, where=0,    
    n=1, size=80) at ./screen.c:894                                             
#8  0x0000000000430434 in ScrnDeleteLine (xw=0x69c100, sb=0x6d3290, last=23,    
    where=0, n=1) at ./screen.c:1122                                            
#9  0x0000000000438ae2 in xtermScroll (xw=0x69c100, amount=1) at ./util.c:543   
#10 0x0000000000415209 in doparsing (xw=0x69c100, c=10, sp=0x6636a0)            
    at ./charproc.c:1680                                                        
#11 0x0000000000418a7e in VTparse (xw=0x69c100) at ./charproc.c:3142            
#12 0x0000000000418bc2 in VTRun (xw=0x69c100) at ./charproc.c:5256              
#13 0x00000000004240f5 in main (argc=0, argv=<value optimized out>)             
    at ./main.c:2414                                                       

Expected results:
I should see the dmesg output

Additional info:

I compiled the source rpm from http://ftp.redhat.com/pub/redhat/linux/enterprise/6Workstation/en/os/SRPMS/xterm-253-1.el6.src.rpm to have debugging symbols for you.

Comment 1 RHEL Program Management 2013-10-13 23:43:29 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 2 Miroslav Lichvar 2014-02-24 18:22:54 UTC
Do you still have the boot.log file which causes the crash?

Comment 3 Schlake 2014-02-24 18:53:33 UTC
Created attachment 867103 [details]
this boot.log crashes an xterm

This boot.log crashes an xterm.  My xterm is xterm-253-1.el6.x86_64.

Method:
 /bin/cat boot.log
 dmesg

I tried it three times, it crashed each time.

Comment 4 Miroslav Lichvar 2014-02-28 15:47:30 UTC
Unfortunately, I still can't reproduce it.

In the upstream changelog for xterm #257 there is an entry that could be this bug. Can you please try these test packages and see if you can reproduce the problem with the first package and not with the second package (it includes the patch from #257)?

http://people.redhat.com/mlichvar/tmp/xterm/xterm-253-1.el6_5.test1.x86_64.rpm
http://people.redhat.com/mlichvar/tmp/xterm/xterm-253-1.el6_5.test2.x86_64.rpm

Comment 5 Schlake 2014-02-28 17:39:09 UTC
Created attachment 869137 [details]
typescript of trying those rpms

I first tried rpm -Uvh followed by xterm, cat /var/log/boot.log then dmesg, and they both crashed.  To make the typescript I had to rpm --force --install since I was downgrading at that point.

Comment 6 Miroslav Lichvar 2014-03-05 11:27:57 UTC
Do you use the default xterm configuration or do you have some xterm resources set (xrdb -query)?

Comment 7 Schlake 2014-03-06 15:38:46 UTC
Created attachment 871528 [details]
output of xrdb -query command

Here is the output of xrdb -query.

In addition, I normally start an xterm with a script containing this line:
   xterm -fa Monospace-12 -rightbar -ls -title $1 -bg black -fg white -cr white -xrm "'XTerm*VT100.translations: #override <Btn1Up>: select-end(PRIMARY, CLIPBOARD, CUT_BUFFER0)'"

But that doesn't seem to be related, as starting a bare xterm without those options also reliably crashes.

Comment 8 Miroslav Lichvar 2014-04-15 12:41:28 UTC
Hm, even with that resources it still doesn't crash for me. There are no other reports like this, so I suspect there may be something unusual in your setup. Do you use a tiling window manager?

Can you please try to reproduce the problem with the latest upstream version? Here is a RHEL6 test build:

http://people.redhat.com/mlichvar/tmp/xterm/xterm-303-1.el6.test4.x86_64.rpm

Comment 9 Miroslav Lichvar 2014-04-15 12:52:50 UTC
Also, running xterm (with debug info) in valgrind could help us.

Comment 10 Schlake 2014-04-16 15:00:33 UTC
Sorry for the late reply, I had surgery.

It no longer crashes with xterm-303-1.el6.test4.x86_64.rpm.

Comment 11 Schlake 2014-04-16 15:01:48 UTC
Oh, and I use KDE pretty much stock with RHEL6.

Comment 12 Miroslav Lichvar 2014-04-16 15:09:45 UTC
Thanks for the information. So it looks like it's fixed in some upstream version since 253.

CCing upstream maintainer. Thomas, do you recall what change could be related to this crash?

Comment 13 Miroslav Lichvar 2016-07-18 10:00:09 UTC
As a workaround, disabling the scrollback buffer with "-sl 0" option may help.

Comment 15 Chris Williams 2016-07-28 22:14:40 UTC
When Red Hat shipped 6.8 on May 10, 2016 RHEL 6 entered Production Phase 2. 
https://access.redhat.com/support/policy/updates/errata#Production_2_Phase
That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released"
Should this BZ be deemed critical please open a Support case in the Red Hat Customer Portal and ask that this BZ be re-opened.