Bug 119549

Summary:	gnome-terminal displays no prompt after reset and clear
Product:	[Fedora] Fedora	Reporter:	Andrew Farris <lordmorgul>
Component:	gnome-terminal	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-05 01:17:14 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 Andrew Farris 2004-03-31 12:04:39 UTC

Description of problem:
gnome-terminal does not re'prompt after the menu command "Terminal ->
Reset and Clear".  It is necessary to enter a blank line (which is a
valid input line.. just lacks prompt) before the prompt is correctly
displayed.

Version-Release number of selected component (if applicable):
gnome-terminal-2.5.90-1.1

How reproducible:
Always

Steps to Reproduce:
1. open gnome-terminal and enter several lines
2. Select "Terminal -> Reset and Clear" from menubar

Actual results:
no prompt is displayed immediately after "Reset and Clear"

Expected results:
prompt should be displayed for the first entered command

This behavior has been present here for a while so is not specific to
this package.

Comment 1 Andrew Farris 2004-10-22 09:26:06 UTC

Behavior still exists in 2.7.3-1 and I see no mention of this upstream, will
move the bug there.

I believe what the terminal is doing may be a literal 'reset, and then clear'
which removes all output of the prompt.  The positioning of the cursor indicates
a prompt was sent (I use a multiline prompt).

Comment 2 Ray Strode [halfline] 2005-08-31 15:17:29 UTC

Hi Andrew,

Did this ever get filed upstream?

Comment 3 John Thacker 2006-05-05 01:17:14 UTC

It probably should be filed upstream, even if it isn't yet.  I can't
find it upstream, although the behavior is still there.