Description of problem: If I use system-config-network to change my ethernet connection to NOT be controlled by NetworkManager, then deactivate it, an empty /etc/modprobe.conf file is generated. There shouldn't even be any code referring to this file anymore, AFAIK. This may explain the mysterious empty modprobe.conf files that many people have seen, that cause warnings on boot. The same thing happens on F12. Version-Release number of selected component (if applicable): system-config-network-1.6.0-2.fc14.noarch How reproducible: always Steps to Reproduce: 1. Use s-c-n to edit ethernet connection so it's not controlled by NetworkManager. 2. Use s-c-n to deactivate the ethernet connection. Actual results: An empty /etc/modprobe.conf file is generated.
Right after installing F13 (AKA RC3) I used s-c-n to edit the ethernet connection to add a DHCP hostname. Upon saving I had an empty /etc/modprobe.conf file. It seems that just about any use of s-c-n to edit network settings triggers this.
Simplified procedure for reproducing: start s-c-n, then File/Save. That's it. The file /etc/modprobe.conf is immediately created.
But, if you close the applet with the x. It doesn't create /etc/modprobe.conf or s-c-n-tui doesn't create it either.
Confirmed - if I run s-c-n-tui and immediately select "Save&Quit", it doesn't create the file. Interesting.
*** Bug 598764 has been marked as a duplicate of this bug. ***
Fixed upstream (commit f6d58b7).
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle. Changing version to '14'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
system-config-network-1.6.1-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/system-config-network-1.6.1-1.fc13
system-config-network-1.6.1-1.fc14 has been submitted as an update for Fedora 14. http://admin.fedoraproject.org/updates/system-config-network-1.6.1-1.fc14
This appears to fix the problem in F13. Can't test in F14 or Rawhide since my VirtualBox guests currently don't work in graphical mode.
system-config-network-1.6.1-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-network'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/system-config-network-1.6.1-1.fc14
Appears to fix the problem in F14 and Rawhide as well, testing in KVM guests. Please submit an update for F12 as well. Thanks.
system-config-network-1.6.1-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
system-config-network-1.6.1-1.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/system-config-network-1.6.1-1.fc12
system-config-network-1.6.1-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update system-config-network'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/system-config-network-1.6.1-1.fc12
system-config-network-1.6.1-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
system-config-network-1.6.1-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.