Bug 8922

Summary:	Anaconda fix fails
Product:	[Retired] Red Hat Linux	Reporter:	saerickson
Component:	installer	Assignee:	Jay Turner <jturner>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	6.1	CC:	saerickson, srevivo
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:	2000-04-17 17:35:44 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 saerickson 2000-01-27 14:51:32 UTC

RedHat's fix for the Anaconda crash doesn't work on my machine.  You
recommend three things (verify the files aren't corrupted, eliminate
the non .rpm files, and use the new install boot disk).  I've done
all three and the only change, after a lot of time is that the error
message after Anaconda/Python crashes the install changes.  It initially
was "unsubscriptable object" and now it's "sndconfig".

Comment 1 Jay Turner 2000-02-09 23:22:59 UTC

If you are no longer getting the error about "unscriptable object" then the fix
that we provided did indeed work.  What error message are you getting now?
Submit those details and we will work to replicate in the test lab.

Comment 2 Jay Turner 2000-02-10 15:41:59 UTC

Anaconda is the installer itself.  I said that the first fixed worked because it
did.  By getting rid of the non-rpm files in the RPMS directory, you are no
longer getting the "unscriptable object" error.  This is because you no longer
have an unscriptable object.

I really need the error message that you are getting relative to sndconfig.
There could be 100 different error message that you are receiving.  These range
from the installer not being able to find the sndconfig package in order to
installer it to the installation of the sndconfig package failed when the
installer attempted to place it on the system.  I have no record of anyone
reporting an error related to sndconfig, so therefore I need some context for
this error, otherwise there is no chance that I am going to be able to replicate
this situation in the lab.