Bug 131049 - Anaconda (26/08) crashes on checking previous Redhat installation
Anaconda (26/08) crashes on checking previous Redhat installation
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-08-26 18:10 EDT by Deji
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-08-27 00:41:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Deji 2004-08-26 18:10:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)

Description of problem:
I was trying to install the today's devel tree, but anaconda was
having this unhandled exception on checking for previous installation.
Last call trace look like this;
File "/usr/src/build/442567-i386/install//usr/lib/anaconda/gui.py,
line 791,  in nextclicked
     self.setScreen ()
File "/usr/src/build/442567-i386/install//usr/lib/anaconda/gui.py,
line 1134,  in setScreen
     new_screen=apply(self.currentwindow.getScreen, args)
line i48,  in getScreen
    iter=model.append (iter)
   TypeError:expecting a sequence.

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

How reproducible:

Steps to Reproduce:
1. Do network install from the development tree

Actual Results:  Installation fails

Expected Results:  Should install successfully

Additional info:

If I may add, (1) there was also an warning messages after retrieving
 'stage2.img' from the ftp server,
/usr/sbin/load_policy Warning! Error whiile getting boolean name, no
such file or directory.
(2) There has been support for my ATI IGP 345M card in xorg for some
time now, but anaconda still doesn't know about it.

Comment 1 Jeremy Katz 2004-08-27 00:41:44 EDT
Already fixed in CVS, will be in the next build.

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