Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 163005

Summary: Install hangs at cracklib-dicts-2.8.2-1-i386
Product: [Fedora] Fedora Reporter: Ra P. <rafapp>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED CANTFIX QA Contact: Mike McLean <mikem>
Severity: high Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-21 21:08:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Ra P. 2005-07-12 06:35:27 UTC
Description of problem:
Install hangs at cracklib-dicts-2.8.2-1-i386

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

How reproducible:
100%. Have downloaded both DVD and CD images, both die.
Have tried both graphical and textual install.

Steps to Reproduce:
1. Use default install
2. Use CD or DVD images
3. After formatting SATA drives, it hangs early in the install
Actual results:
Install hangs. Have tried both graphical and textual install.

Expected results:
Install installs.

Additional info:
Dell 400SC with 2 320GB SATA drives.

Comment 1 Ra P. 2005-07-12 08:10:25 UTC
it just dies on the first thing it installs.
this was the server install fwiw.

this was my first install. 
I am giving up on fedora and switching to debian.

Comment 2 Jeremy Katz 2005-07-12 15:15:20 UTC
Did you verify your media according to the instructions at

Comment 3 Jeremy Katz 2005-09-21 21:08:38 UTC
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.