Bug 705669

Summary: Default bash PROMPT_COMMAND setting interprets escape codes in USER/PWD
Product: Red Hat Enterprise Linux 6 Reporter: Alex Jurkiewicz <alex>
Component: setupAssignee: Ondrej Vasik <ovasik>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0CC: prc, rrakus
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-18 13:51:36 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:

Description Alex Jurkiewicz 2011-05-18 03:13:38 UTC 
Description of problem:
The default PROMPT_COMMAND values set in /etc/bashrc interpret backslash escapes in $USER, $HOSTNAME and $PWD. This causes junk to be printed before the prompt if certain escape sequences are encountered, when any sequences should be printed literally.

Version-Release number of selected component (if applicable):
/etc/bashrc distributed with Bash in RHEL4.8 (3.00.15), RHEL5.5 (3.2.25) and RHEL6.0 (4.1.2).

How reproducible:
Always.

Steps to Reproduce:
$ cp /etc/skel/.bashrc ~
$ bash -il
$ mkdir 'foo\abar'
$ cd foo\\abar
Examine prompt, 'bar' appears at the beginning.

Or log on with a username containing an escape code (DOMAIN\alex) and examine prompt.
  
Actual results:
bar[alex@server foo\abar]$ 


Expected results:
[alex@server foo\abar]$ 

Additional info:
Fixed versions:
xterm: PROMPT_COMMAND='echo -ne "\033]0;" ; echo -nE "${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}" ; echo -ne "\007"'
screen: PROMPT_COMMAND='echo -ne "\033_" ; echo -nE "${USER}@${HOSTNAME%%.*}:${PWD/#$HOME/~}" ; echo -ne "\033\\"'
Comment 2 Roman Rakus 2011-05-18 13:22:13 UTC 
Thanks for the report. However bash is not right component, /etc/bashrc is part of setup package.
Comment 3 Roman Rakus 2011-05-18 13:51:36 UTC 

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