Description of problem:
Selecting Fedora Extras in the current FC6 respin fails (even with dynamic IP)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Rebuild the installation DVD with all updates using pungi.
2. Try installing FC6 from that DVD.
3. Select dhcp in the network configuration.
4. Select Fedora Extras in the package selection dialog
5. Select the wired interface and dhcp and click OK
An "Exception occurred" dialog appears. It reads:
Traceback (most recent call first):
File "/usr/lib/anaconda/iw/netconfig_dialog.py", line 215 in _ok
_("Error configuring network device")
TypeError: parent should be a GtkWindow or None
Local variables in innermost frame:
self: <netconfig_dialog.NetworkConfigurator instance at 0xb7bf550c>
args: (<gtk.Button object (GtkButton) at 0xb19f284>,)
w: <gui.WaitWindow instance at 0xab721ac>
combo: <gtk.ComboBox object (GtkComboBox) at 0xb19f2ac>
active: <GtkTreeIter at 0xa9a9258>
The interface is brought up and Fedora Extras becomes available, or at least I
get an error message from which I can recover.
This is not bug #212018 (AnacondaExtrasConfig). This bug happens with the
updated current Anaconda and doesn't require static address to be selected.
There are two network interfaces on the system: Intel wired (e1000) and Intel
wireless (ipw-3945). The wireless interface is not detected. The wired
interface is detected and is registered as eth0 with the e1000 driver. I can
see it by doing:
ls -ald /sys/class/net/eth0/device/driver
on the text console after the failure. I select eth0. I know that it sometimes
fails to detect carrier, but it's not an excuse for a failure with traceback.
Moreover, I brought eth0 up manually and I see the carrier (cat
/sys/class/net/eth0/carrier gives 1).
I believe the message is caused by incorrect use of the first argument to
gtk.MessageDialog, which should be a window (e.g. self.parent as in
partition_gui.py and raid_dialog_gui.py) or None.
netconfig_dialog.py passes a string instead in two places, on lines 135 and 213.
I also tested the same disk on another system with no problems with carrier, and
I'm still getting the same problem. Apparently, there is also a failure to
obtain an IP address in addition to the problem displaying the error message.
Respins don't include updated anaconda builds. While your problem isn't
AnacondaExtrasConfig, it's another relatively often reported FC6 bug that's
fixed in anaconda-220.127.116.11.
*** This bug has been marked as a duplicate of 213356 ***