Bug 58418 – Installer crashed when 'selecting packages'

Bug 58418 - Installer crashed when 'selecting packages'

Summary:	Installer crashed when 'selecting packages'

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i686 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Brent Fox
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-01-16 04:41 EST by Rob K
Modified:	2007-04-18 12:39 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-01-16 04:42:58 EST
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 04:42 EST, Rob K	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Rob K 2002-01-16 04:41:55 EST

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 04:42:53 EST

Created attachment 42574 [details]
anaconda traceback

Comment 2 Michael Fulbright 2002-01-16 14:26:15 EST

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.