Bug 64078

Summary: boot install from CD halted with error message. Saved a copy of the file.
Product: [Retired] Red Hat Linux Reporter: John King <johnhlk>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: low    
Version: 7.0   
Target Milestone: ---   
Target Release: ---   
Hardware: other   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:48:47 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:
Attachments:
Description Flags
Install error ANACDUMP none

Description John King 2002-04-25 05:27:06 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90)

Description of problem:
Atempting to get my head around a better OS than Windows decided to load Linux. 
Being a novice needed several attempts and still haven't been entirely 
sucessful. Still having trouble figuring out LILO! On one attempt install 
halted with an error message and this shouldn't happen. Also produced the 
attached file which I managed to save in my win OS. 

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


How reproducible:
Didn't try

Steps to Reproduce:
1.Just happened once
2.
3.
	

Additional info:

Traceback (innermost last):
File
"/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run

Comment 1 John King 2002-04-25 05:30:14 UTC
Created attachment 55225 [details]
Install error ANACDUMP

Comment 2 Michael Fulbright 2002-04-26 19:24:39 UTC
What are the individual steps required to get to this error?

Can you make it happen over and over?

Comment 3 Michael Fulbright 2002-05-23 16:54:11 UTC
Closing due to inactivity - please reopen if you have additional comments to add
to this bug.

Comment 4 Red Hat Bugzilla 2006-02-21 18:48:47 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.