Created attachment 626221 [details] the error, when returning to the main hub Description of problem: It is possible to remove all networking connections and then when one returns to the main hub, an un-abrt-able 'unknown error' will pop-up. Since there is no more network, it cannot be reported back. Version-Release number of selected component (if applicable): F18b TC3 How reproducible: always Steps to Reproduce: 1. enter network 2. double click the 'configure' button 3. remove shown network connections 4. return to the main hub Actual results: unknown error, cannot be reported back via abrt, and one must reboot and retry. Expected results: no error or a way to repair the damage Additional info: the lack of an 'ifconfig' command (i don't know why it is not there...) prevents the network reconfiguration from the command line. (and also prevents abrt from working).
Created attachment 626250 [details] snapshot of the screen, delete the network connections
ifconfig is deprecated in favour of iproute2 package (ip command). The dialog with list of connections where you was able to delete them is a result of the second click of your double click. This UI shouldn't be available to user at all. I've sent a patch making nm-c-e more modal - making Configure button insensitive while nmce is running.
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18
Package anaconda-18.19-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-18.19-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16528/anaconda-18.19-1.fc18 then log in and leave karma (feedback).
This bug looks to have been fixed for many anaconda builds now but missed being closed. If you find you are still experiencing it with Fedora 18 Beta (RC1) or later, please re-open the bug.