Bug 439617

Summary: Text installation of Fedora 9 beta (from DVD) fails
Product: [Fedora] Fedora Reporter: Chris Ross <cross+redhat>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-29 22:50:58 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Chris Ross 2008-03-29 17:24:43 UTC
Description of problem:

When conducting a text installation (in my case, because I had 192MB memory and it auto-chose a text 
installation), after package selection and disk configuration, anaconda will fail with a python exception 
that after reading through looks like it may be related to trying to deal with an upper-ASCII character 
somewhere.  I'm not sure which package it is, but it's one of the first dozen or two.

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

Fedora 9 beta (DVD)

How reproducible:

- Perform a text installation of Fedora 9 beta from the DVD
- Selection of "Office and Productivity" or "Software development" doesn't affect the outcome.  With 
both deselected, the error occurs

Steps to Reproduce:
1. Start a text installation from Fedora 9 beta DVD
2. Set up disk however you want
3. Install the default set of packages
  
Actual results:

After the first few packages install, a mini-window will appear in the middle of the screen describing a 
python exception that was thrown.


Expected results:

Successfully installation of all packages

Additional info:

this appears to *not* occur using the graphical installer.  In reading the exception output, I think it's 
some sort of upper-ASCII character encoding issue, which likely can't decode/display properly by the 
text installer.

Comment 1 Chris Lumens 2008-03-29 22:50:58 UTC

*** This bug has been marked as a duplicate of 437993 ***