Red Hat Bugzilla – Bug 177440
Installer crashed at gui.py line 1195 (handleRenderCallback)
Last modified: 2007-11-30 17:11:20 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050922 Fedora/1.0.7-1.1.fc3 Firefox/1.0.7
Description of problem:
See contents of anacdump.txt (attached).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Run setup on VmWare virtual machine (GSX Server 3.2.0 build-14497)
2.Choose IDE hard drives (SCSI drives are not recognized!)
3.Installer fails after choosing system components.
Actual Results: See contents of anacdump.txt (attached).
Expected Results: Installer should have completed installing components to virtual machine.
Traceback (most recent call last):
File "/usr/lib/anaconda/gui.py", line 1195, in handleRenderCallback
File "/usr/lib/anaconda/iw/progress_gui.py", line 245, in renderCallback
File "/usr/lib/anaconda/gui.py", line 924, in nextClicked
File "/usr/lib/anaconda/dispatch.py", line 145, in gotoNext
File "/usr/lib/anaconda/dispatch.py", line 216, in moveStep
rc = apply(func, self.bindArgs(args))
File "/usr/lib/anaconda/backend.py", line 145, in doInstall
backend.doInstall(intf, id, instPath)
File "/usr/lib/anaconda/yuminstall.py", line 752, in doInstall
self.ayum.run(self.instLog, cb, intf)
File "/usr/lib/anaconda/yuminstall.py", line 363, in run
File "/usr/lib/anaconda/yuminstall.py", line 431, in populateTs
for txmbr in self.tsInfo.getMembers():
File "/usr/lib/anaconda/sortedtransaction.py", line 86, in getMembers
KeyError: ('enscript', 'i386', '0', '1.6.1', '31')
Full anacdump.txt file attached to this bug.
Created attachment 123005 [details]
Ouput of anaconda dump facility.
Created attachment 123180 [details]
I have a similar problem when installing and/or upgrading from the Fedora
development tree. This part of the installation was running fine with same
media and system on previous days. Today I got this error.
Joe - What package selections did you make during installation?
Robbie - You are seeing a different problem that should be getting handled
Most likely it was the "server" package set, but I can't be 100% sure.
*** This bug has been marked as a duplicate of 173845 ***