Bug 68695 - gnome-terminal doesn't change title with su(1) to another user
Summary: gnome-terminal doesn't change title with su(1) to another user
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: gnome-terminal   
(Show other bugs)
Version: limbo
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact:
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-07-12 16:11 UTC by Horst H. von Brand
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-07-12 16:24:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Horst H. von Brand 2002-07-12 16:11:00 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020625

Description of problem:
When su(1)ing to root in a gnome-terminal, its title doesn't change to reflect
the new user

Version-Release number of selected component (if applicable): gnome-terminal-2.0.0-3


How reproducible:
Always

Steps to Reproduce:
1.su - root
2.
3.
	

Actual Results:  Title doesn't change
Expected Results:  New title reflecting the new user

Additional info:  Thank you all very much!
Comment 1 Nalin Dahyabhai 2002-07-12 16:23:59 UTC 
In this case it's likely bash setting the title using the value of $USER.  My
best guess is that you're not using "su -", so the value in the shell's
environment remains unchanged, so $USER is your actual user name.

Try using 'su -'.  This should set $USER to "root", which should cause bash to
print the correct prompt.
Comment 2 Havoc Pennington 2002-07-12 16:25:34 UTC 
gnome-terminal isn't setting the title, it's your shell. Nalin's advice should work.
Note You need to log in before you can comment on or make changes to this bug.