Bug 120587 - Installer crashes reporting anaconda keyerror reading glibc
Summary: Installer crashes reporting anaconda keyerror reading glibc
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-04-11 14:44 UTC by Bill Scholz
Modified: 2007-04-18 17:05 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-04-11 18:42:55 UTC
Embargoed:

Attachments (Terms of Use)
Installer error dump (40.55 KB, text/plain)
2004-04-11 14:48 UTC, Bill Scholz 		no flags Details
View All

Description Bill Scholz 2004-04-11 14:44:07 UTC 
Description of problem:
During initial install on a 400 Mhz AMD K6 system, install aborts 
with Anaconda reporting a 'KeyError: glibc'.  Error occurs using 
either "boot: install" or "boot: manual".  Error occurs with either a 
RedHat 7.2 or 7.3 install CD.  

Version-Release number of selected component (if applicable):
Linux version 2.4.7-10BOOT  (Red Hat Linux 7.1 2.96-98)

How reproducible:
100%

Steps to Reproduce:
1.Start boot from CD
2.Type either 'install' or 'manual'
3.Follow typical install dialog
  
Actual results:
Installer reports message that unexpected event has occurred, 
probably a bug, and offers to save the detailed bug summary.  
(Summary has been appended to the Description above)

Expected results:
Normal boot.

Additional info:
This error occurs on initial attempt to install RedHat Linux 7.2 or 
7.3 on an Amd K6 system, 384 MB RAM, 8 GB hd.
Comment 1 Bill Scholz 2004-04-11 14:48:17 UTC 
Created attachment 99314 [details]
Installer error dump

Error dump associated with bug 120585.
Comment 2 Jeremy Katz 2004-04-11 18:42:55 UTC 
This sounds like bad media.  This is handled better in newer releases.
 Please note that Red Hat Linux 7.2 is no longer a supported release.
Note You need to log in before you can comment on or make changes to this bug.