Bug 54832 - Anaconda crashes displaying Release Notes
Summary: Anaconda crashes displaying Release Notes
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Brent Fox
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-10-20 14:22 UTC by Michel Alexandre Salim
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-10-22 21:18:21 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Michel Alexandre Salim 2001-10-20 14:22:31 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.75 [en] (Win95; U)

Description of problem:
If the Release Notes are being displayed at the same time that the installer asks for the CD to be changed, the installer crashes. Found 
this out since the first time I tried installing 7.2 Anaconda crashed after the package tetex-fonts, the second time (not displaying Release 
Notes this time) it went fine.

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

How reproducible:
Didn't try

Steps to Reproduce:
1. Follow installation steps until Anaconda starts installing packages
2. Display Release notes
3. Wait until installer asks for next CD

Actual Results:  Anaconda crashes, dumps error messages

Expected Results:  Dialog box asking for next CD appearing on top of 'Release Notes' window

Additional info:

Note: This is actually for 7.2 but it's not available yet for selection in Bugzilla (yes, I bought the boxed set). The USB support in installer is 
great guys !

Comment 1 Brent Fox 2001-10-22 21:18:15 UTC
Changing component to 7.2 since it's available now.

Comment 2 Brent Fox 2001-10-22 21:45:47 UTC
I was unable to duplicate this behavior.  I can't explain why it would fail for
you once but then work the next time.  Please reopen this bug if you can
reproduce it reliably.  Thanks for your report.

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