Bug 447254 - Method string is not assigned correctly
Summary: Method string is not assigned correctly
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 9
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-19 06:01 UTC by The Source
Modified: 2008-08-04 15:30 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-04 15:30:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description The Source 2008-05-19 06:01:31 UTC
Description of problem:
There is a bug in nv modules which does not allow me to install F9 correctly
with my GeForce 8800 GTX. So I decided to use vesa driver. I loaded in rescue
mode and launched anaconda manually:
anaconda --xdriver=vesa --method=cdrom -G
But when I passed boot loader config screen anaconda gave crash dialog with a
lot of text but the main error message was:
Methodstr was referenced before assigned.

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

How reproducible:
always

Steps to Reproduce:
1. Load in rescue mode
2. anaconda --xdriver=vesa --method=cdrom -G
3. continue until boot loader config screen and press Next.
  
Actual results:


Expected results:


Additional info:

Comment 1 Chris Lumens 2008-05-19 13:29:52 UTC
We'll need the complete error message with line numbers and everything in order
to fix this.

However, what happens if you pass the correct form of the method string?  That
is, something like:  --method=cdrom:///dev/sr0:/mnt/source

Comment 2 The Source 2008-05-20 16:04:34 UTC
Tried it. Didn't help, but the error message is different with your string:
TypeError: coe.blah..forgot unicode: expected String, got NoneType.

Comment 3 Chris Lumens 2008-05-20 16:12:34 UTC
Please attach the complete error message to this bug report.


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