Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 58458 - installler crashed giving error in attached file
installler crashed giving error in attached file
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-01-17 02:41 EST by Tim
Modified: 2007-04-18 12:39 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:48:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
anaconda dump (76.08 KB, text/plain)
2002-01-17 02:42 EST, Tim
no flags Details
another dump. (19.00 KB, text/plain)
2002-01-29 05:02 EST, Tim
no flags Details

  None (edit)
Description Tim 2002-01-17 02:41:50 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:

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

How reproducible:
Didn't try

Additional info:
Comment 1 Tim 2002-01-17 02:42:25 EST
Created attachment 42674 [details]
anaconda dump
Comment 2 Jeremy Katz 2002-01-21 20:46:55 EST
Was this to be a dual boot system?
Comment 3 Tim 2002-01-21 21:06:16 EST
no it was on a completely formatted drive.
Comment 4 Tim 2002-01-29 05:02:30 EST
Created attachment 43876 [details]
another dump.
Comment 5 Jeremy Katz 2002-03-07 16:41:41 EST
These are in seemingly random locations where the code obviously exists... if
these are cds you burned yourself, could you check the md5sums versus those
published on our ftp site?
Comment 6 Michael Fulbright 2002-04-10 14:23:09 EDT
Closing due to inactivity, please reopen if you contine to have problems.
Comment 7 Red Hat Bugzilla 2006-02-21 13:48:20 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.