Bug 86171 - Update created new error, can't install
Update created new error, can't install
Product: Red Hat Linux
Classification: Retired
Component: installer (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2003-03-15 12:51 EST by Nield Rankosa
Modified: 2007-04-18 12:52 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-22 12:30:37 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 Nield Rankosa 2003-03-15 12:51:53 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
I originally had a problem with installing that came right after formatting, 
when it was about to install. I went and downloaded an update, put it on a disk 
as directed, and typed linux updates in the initial boot screen. It read the 
updates and proceeded to initialize the installation program. I then get this 

Traceback (most recent call last):
  File "/usr/bin/anaconda", line 594, in?
    intf.progressWindow, rootPath)
TypeError: __init__() takes exactly 3 arguments (5 given)
install exited abnormally

The update image file was named 8.0-cdread.img

Nield Rankosa

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

How reproducible:

Steps to Reproduce:
1. Download update specified above
2. Initialize installation using 'linux updates'
3. Allow installation to read update disk and proceed to graphical installation 

Actual Results:  I get the error specified in the description.

Expected Results:  I expect the updates to fix the previous error and continue 
to install.

Additional info:
Comment 1 Michael Fulbright 2003-03-17 14:23:40 EST
Could you give the URL of the update image you are using?
Comment 2 Nield Rankosa 2003-03-18 01:42:14 EST
Comment 3 Jeremy Katz 2003-03-21 17:42:16 EST
The image looks fine to me here -- can you attach the complete dump you receive?
Comment 4 Michael Fulbright 2003-04-22 12:30:37 EDT
Closing due to inactivity. If you have new information to add please reopen the
issue report.

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