Bug 1003118

Summary: Unable to get correct display when remotely logged onto HP-UX B.11.31
Product: [Fedora] Fedora Reporter: Philippe Vouters <Philippe.Vouters>
Component: initscriptsAssignee: Bill Nottingham <notting>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: iarlyy, jonathan, lnykryn, mlichvar, notting, pertusus, plautrba, rvokal, vpavlin
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-02 09:33:21 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:

Description Philippe Vouters 2013-08-30 21:27:24 UTC 
Description of problem:
echo $TERM xterm terminal now displays under F19 the string "xterm-256color".
HP-UX B.11.31 (other Unix systems ????) expects "xterm". Now get poor display when remotely logged onto HP-UX.

Version-Release number of selected component (if applicable):
[philippe@victor ~]$ rpm -qa | grep xterm
xterm-293-1.fc19.i686


How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
HP-UX uncomfortable remote terminal display as it does not recognize xterm-256color for $TERM
xterm today unfitted for correct work with HP-UX. Do not know which Linux terminal displays $TERM as xterm instead of xterm-256color

Expected results:
Unusable Linux terminal when remotely logged onto HP-UX B.11.31. 

Additional info:
Comment 1 Philippe Vouters 2013-08-30 21:52:48 UTC 
Is Linux slowly becoming more and more Unix incompatible ? Becoming proprietary like Windows ?????

Today workaround when remote logged to an HP-UX B.11.31 computer;
$ export TERM=xterm
With such an export, the display now gets correct for both xterm and aterm when performing HP-UX man cc.
Comment 2 Miroslav Lichvar 2013-09-02 09:33:21 UTC 
Yes, this is a known problem of the automatic 256 color setting. It was added in Fedora 18. The problem with remote side not supporting the terminfo was documented in the release notes.

Please see:

http://fedoraproject.org/wiki/Features/256_Color_Terminals#Unsetting_256_color_on_the_remote_system
Comment 3 Philippe Vouters 2013-09-02 11:15:04 UTC 
Dear Red Hat employee,

Your answer was the best you could currently do to this Bugzilla Red Hat report.

Forcing:
export TERM=xterm
to my xterm case in my Linux ~/.bash_profile was the best action I could make matching the environment I work with under both Linux and HP-UX.

Simply stated, HP-UX is strongly bound to Unix standards like any Unix operating system. This does not look to be as committing for Linux. I simply hope that Linux shall keep enough Unix compatibility over time.

I CC on this HP support staff people of my knowledge so that the information gets spread.
Comment 4 Bill Nottingham 2013-09-03 14:33:39 UTC 
FYI, the xterm-256color terminfo entry was added to the terminfo database of the ncurses package in 1999, and further support in the ncurses library itself was added in 2005. ncurses is, as far as I know, a pretty generic Unix package portable to HP-UX and other systems, and is no way "proprietary like Windows."

Hope that helps, and have a nice day.