Bug 58826

Summary: installer exits giving "error in line 620" messsage
Product: [Retired] Red Hat Linux Reporter: Sayed <saosman>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED NOTABUG QA Contact: Brock Organ <borgan>
Severity: high Docs Contact:
Priority: high    
Version: 7.2CC: brendan_j_molloy
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:48:22 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
the saved log provided by the installer none

Description Sayed 2002-01-25 12:37:07 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; Win 9x 4.90)

Description of problem:
installing went smoothly untill the step of "marking the packages to be 
installed" and it spontaneously gave an error telling that there is a bug in 
the file "anaconda" line 620..

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


How reproducible:
Always

Steps to Reproduce:
1.Just follow the insaller and it would be produced...
2.
3.
	

Actual Results:  The installer exits ejecting my CD and giving the message "it 
is safe now to reboot your system"

Expected Results:  Insatllation should complete...

Additional info:

This is the first time for RedHat Linux to be distributed in Egypt (with 
the "On-Line" magazine) and indeed it left a very bad impression about linux 
operating system in general,
i am sorry for that...
Comment 1 Sayed 2002-01-25 12:43:02 UTC 
Created attachment 43455 [details]
the saved log provided by the installer
Comment 2 Michael Fulbright 2002-01-29 17:31:48 UTC 
Any ideas Matt?
Comment 3 Matt Wilson 2002-02-12 00:26:08 UTC 
How much ram, what brand of motherboard, and what's your IDE configuration?

Looks like on-disk corruption when writing to the disk.
Comment 4 Brent Fox 2002-03-12 16:28:26 UTC 
saosman, any more info here?
Comment 5 Michael Fulbright 2002-04-10 18:21:39 UTC 
Closing due to inactivity, please reopen if you contine to have problems.
Comment 6 Red Hat Bugzilla 2006-02-21 18:48:22 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.