Bug 58418 - Installer crashed when 'selecting packages'
Summary: Installer crashed when 'selecting packages'
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.2
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-16 09:41 UTC by Rob K
Modified: 2007-04-18 16:39 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-01-16 09:42:58 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
anaconda traceback (37.01 KB, text/plain)
2002-01-16 09:42 UTC, Rob K 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Rob K 2002-01-16 09:41:55 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20011226

Description of problem:
Installing on a 486dx2/66 with 48M RAM and 1Gig HD

Installer crashes after selecting the timezone, then getting package list - 
produces anaconda traceback.

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


How reproducible:
Always

Steps to Reproduce:
1. Boot off bootnet floppy - installing off planetmirror.com
2. Go through install process.
3. Installer refuses to autopartition drive, so create manually
4. Splat!
	

Actual Results:  Installer hangs, produces python traceback, prompts for a
floppy disk to save same

Expected Results:  Product should install.

Additional info:
Comment 1 Rob K 2002-01-16 09:42:53 UTC 
Created attachment 42574 [details]
anaconda traceback
Comment 2 Michael Fulbright 2002-01-16 19:26:15 UTC 
This happens when there is corruption - I would recommend trying a different
mirror as the one you were using appears to have a bad copy.
Note You need to log in before you can comment on or make changes to this bug.