Description of problem: Transitioning to stage#2 of the install fails. Version-Release number of selected component (if applicable): * anaconda-12.6 How reproducible: * Everytime Steps to Reproduce: 1. Attempt a rawhide install using anaconda-12.6 2. Provide lang and keyboard and installation source Actual results: 13:26:51 Starting VNC... Traceback (most recent call last): File "/usr/bin/anaconda", line 870, in <module> runVNC() File "/usr/bin/anaconda", line 356, in runVNC vncS.startServer() File "/usr/lib/anaconda/vnc.py", line 208, in startServer self.initialize() File "/usr/lib/anaconda/vnc.py", line 102, in initialize netinfo = network.Network() File "/usr/lib/anaconda/network.py", line 342, in __init__ available_devices = self.available() File "/usr/lib/anaconda/network.py", line 393, in available self.netdevices[dev].set(('DESC', isys.getNetDevDesc(dev))) File "/usr/lib/anaconda/isys.py", line 603, in getNetDevDesc if dev.has_key("ID_VENDOR_ENC") and dev.has_key("ID_MODEL_ENC"): AttributeError: 'NoneType' object has no attribute 'has_key' install exited abnormally [1/1] disabling swap... unmounting filesystems... /mnt/runtime done disabling /dev/loop0 LOOP_CLR_FD failed: 16 /proc done /dev/pts done /sys done /selinux done sending termination signals...done sending kill signals...done you may safely reboot your system Expected results: * stage#2 starts without error Additional info:
This is actually fixed in git, we just didn't do a new build as networking was still falling over like it was yesterday
Created attachment 355722 [details] console log (includes kernel trace) I also got this bug, although I did it through a serial console rather than VNC, and it includes a kernel trace following the anaconda trace. [ INFO: possible recursive locking detected ] 2.6.31-0.107.rc4.git3.fc12.i686 #1 [Details in attachment.]
Allen: Thanks for logging the kernel trace as well. I'm tempted to suggest logging this as a separate issue, but I suspect that given it's non-urgent nature it might not get a lot of attention. However, it can't hurt to record it.
(In reply to comment #4) > Allen: Thanks for logging the kernel trace as well. I'm tempted to suggest > logging this as a separate issue, but I suspect that given it's non-urgent > nature it might not get a lot of attention. However, it can't hurt to record > it. I already filed that as bz 514555.
I got similar error when trying to start a graphical install. Picture of screen after crash is attached
Created attachment 355880 [details] Picture of screen after crash
The installation images from 2009-08-01 fixed my issue.
(In reply to comment #8) > The installation images from 2009-08-01 fixed my issue. Agreed. Fixed with boot.iso of 01-Aug-2009, but now I'm hitting Bug 513104.
Closing as per comments 8 and 9.