Red Hat Bugzilla – Bug 168396
Created installer fail after Required Install Media
Last modified: 2007-11-30 17:11:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.7.10-1.5.2
Description of problem:
Have created Installed discs with current updated version of gtk2.
We go through the process to install FC4-updated
using graphical install option.
That means, the text install already succeed without provided patch.
Steps to reproduce.
After the information dialog telling you the required discs.
The installation terminate with following information.
Traceback (most recent call last):
File "/usr/lib/anaconda/gui.py", line 876, in nextClicked
File "/usr/lib/anaconda/gui.py", line 1198, in setScreen
new_screen = apply(self.currentWindow.getScreen, args)
File "/usr/lib/anaconda/iw/progress_gui.py", line 335, in getScreen
progressTable.attach (self.totalProgress, 1, 2, 0, 1, ypadding=2)
TypeError: GtkTable.attach() argument 8, item 14711675, item 2271359, item 383,
David Woodhouse has given hint on the fedora mailing about this problem.
I have ask him to provide a patch.
The patch was having the following lines, tell us that it is a backport.
--- iw/progress_gui.py.yy 2005-05-23 16:11:06.000000000 -0400
+++ iw/progress_gui.py 2005-09-13 02:45:36.000000000 -0400
cvs access has confirm presence of the change.
After rebuilding the installation with the patched anaconda package.
The graphical installation has completed successfully.
i have included the patch has attachment
thanks to David,
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. see Description above
Actual Results: see Description above
Created attachment 118863 [details]
Anaconda in FC4 is fine with what shipped _in FC4_. We don't support rebuilt
trees for reasons just like this. It's actually a pygtk2 bug that's fixed in
(In reply to comment #2)
my guest here is that the bug was present before
means, i can not confirm the faulty version.
I comment only to help localize version with the bad behavior.
the traceback must be enough clear to know if your is a bad one.
*** This bug has been marked as a duplicate of 168338 ***