Bug 66326

Summary: missing file: gdm-2.2.3.1-22.i386.rpm at installation
Product: [Retired] Red Hat Linux Reporter: Ken Wise <wise>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED NOTABUG QA Contact: Aaron Brown <abrown>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
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:49:03 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 Ken Wise 2002-06-07 20:28:04 UTC
Description of Problem:
Technician Phillip Morales directed me to your site:  Service Request 207077
Installing Linux Personal 7.3    Installation appeared to recognize all
devices on the computer: HP tower.   Installation was flawless on CD #1.
Inserted CD #2.  Ran for a couple minutes and stopped with Error Message:
missing file: gdm-2.2.3.1-22.i386.rpm
Cleaned cd rom 3 times
re-started installation - same message.

After requesting service from Tech, he directed me to bugzilla.

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


How Reproducible:
Install RedHat Linux Personal 7.3

Steps to Reproduce:
1. Clear hard drive
2. Run install
3. Follow instructions

Actual Results:
Error message: missing file.

Expected Results:
Successful installation

Additional Information:
Service Request # 207077
Customer # 400067
Customer Name Ken Wise
wise

Comment 1 Jeremy Katz 2002-06-21 21:29:23 UTC
From the basic description, it sounds like you have a bad CD.  Could you check
your CD following the instructions at http://people.redhat.com/~msf/mediacheck.html?

Comment 2 Michael Fulbright 2002-07-15 16:55:43 UTC
Closing due to inactivty, please reopen if you have additional information to add.

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:03 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.