Bug 845649 – text-based kickstart doesn't print to screen correctly

Bug 845649 - text-based kickstart doesn't print to screen correctly

Summary:	text-based kickstart doesn't print to screen correctly

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	anaconda (Show other bugs)
Sub Component:
Version:	17
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Anaconda Maintenance Team
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-08-03 13:52 EDT by joshua
Modified:	2012-08-07 09:36 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-08-07 09:36:16 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
bad text updates to the screen (2.38 MB, image/jpeg) 2012-08-03 13:52 EDT, joshua	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description joshua 2012-08-03 13:52:23 EDT

Created attachment 602172 [details]
bad text updates to the screen

Description of problem:

See screenshot.  Packages installed have their description written to the screen in a way that doesn't update cleanly.  Only the first packages description is written to the screen, nothing else updates.


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

F17 x86_64

Comment 1 Vratislav Podzimek 2012-08-07 09:36:16 EDT

I can confirm such behaviour with the only difference -- description of the first package stays on the screen while every other package's description is correctly shown above that.
However, there will be whole new TUI not using newt in the next release, so this will be surely fixed. Closing as NEXTRELEASE.

Note You need to log in before you can comment on or make changes to this bug.