Created attachment 356528 [details] bug demonstration Description of problem: I'm installing Fedora 12 Alpha TC: http://alt.fedoraproject.org/pub/alt/stage/12-Alpha-TC/Fedora-12-Alpha-x86_64-DVD/ from netinst image in virt-manager (using KVM). When choosing install source the NFS dialog box causes exceptions. Version-Release number of selected component (if applicable): * anaconda-12.7 * virt host - Fedora 11, libvirt-0.6.2-13.fc11.x86_64 How reproducible: so far always Steps to Reproduce: 1. Boot from F12 Alpha TC netinst 2. Select NFS install and leave everything blank 3. Click OK, OK on error, Cancel 4. Click Modify repository again 5. exception Actual results: Exception Expected results: No exception Additional info: See attached logs and video. "Save" button under exception does not work, therefore only some logs are available.
Created attachment 356529 [details] anaconda.png
Created attachment 356530 [details] logs.tar.gz
The traceback in the anaconda.png is about python-meh, and that's been fixed. The original traceback is: anaconda 12.7 exception report Traceback (most recent call first): File "/usr/lib/anaconda/iw/task_gui.py", line 178, in createDialog self.nameEntry.set_text(self.repo.name) File "/usr/lib/anaconda/iw/task_gui.py", line 495, in _editRepo dialog.createDialog() TypeError: GtkEntry.set_text() argument 1 must be string, not None
Reviewed during F-12-Alpha Blocker bug meeting. Modifying yum repositories during installation will be discouraged for the Alpha in favor of performing any yum repo operations in the post-installation environment. Ideally, one can perform a NFS installation when booting the boot.iso or DVD with the boot argument: "askmethod" However, that appears to be inoperable for F-12-Alpha (see bug#515450). To perform a NFS installation, it is recommended that you install from a PXE server or using the media-less instructions (see http://docs.fedoraproject.org/install-guide/f11/en-US/html/ap-medialess-install.html). Adjusting the title of this defect to match the failure case.
This should be fixed in anaconda-12.17.
Confirmed to be fixed.