Description of problem: When in the network configuration screen in order to configure an interface, you need to click the configure-button twice to open the configuration window. Version-Release number of selected component (if applicable): 20-Beta-TC2 How reproducible: Everytime Steps to Reproduce: 1. Start a Fedora installation 2. From the central pane, select the network configuration window 3. Click the configuration-button. Configuration window is not opening 4. Click the configuration-button once again. Configuration windows is opening Actual results: Need to click the button twice Expected results: Clicking on the button should open the windows immediatly. Additional info:
Here is updates image for 20-Beta-TC2 with a patch that should fix the issue: http://rvykydal.fedorapeople.org/updates.configure.img
Created attachment 812118 [details] Anaconda.log Patch works, but with this patch static ip adresses are not accepted, as Anaconda did without the patch. I test this on a network segment, without DHCP. I add the IPv4 and IPv6 addresses in the network configuration form. Before the patch Addresssing was not accepted, only after I toggled the NIC on/of switch. With this patch switching the NIC off and on again has no effect. Status stays 'Connecting...' In the log I see that anaconda want to switch back to DHCP. But of course this does not give an address as DHCP is not active.
Thank you for testing and the catch, fixed version of the patch (where swithching NIC on and off should work again) is in this updates image: http://rvykydal.fedorapeople.org/updates.configure2.img
updates.configure2.img works. But the NIC stays in 'Connecting...' state after configuration. I still have to toggle the on/off switch to get it in 'Conntected'-state. Should I file a seperate bug or is this related to this bug?
(In reply to A.J. Werkman from comment #4) > updates.configure2.img works. But the NIC stays in 'Connecting...' state > after configuration. I still have to toggle the on/off switch to get it in > 'Conntected'-state. > > Should I file a seperate bug or is this related to this bug? I think it is the issue of bug #1018471 filed by you.
anaconda-20.25.2-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.2-1.fc20
Package anaconda-20.25.2-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-20.25.2-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-19692/anaconda-20.25.2-1.fc20 then log in and leave karma (feedback).
anaconda-20.25.8-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/anaconda-20.25.8-1.fc20
pykickstart-1.99.46-1.fc20, python-blivet-0.23.5-1.fc20, anaconda-20.25.9-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.