Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #589593 +++
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.
--- Additional comment from andre.edu on 2010-05-22 16:22:39 EDT ---
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.
--- Additional comment from andre.edu on 2010-05-27 23:35:32 EDT ---
Simplified procedure for reproducing: start s-c-n, then File/Save. That's it. The file /etc/modprobe.conf is immediately created.
--- Additional comment from frankly3d on 2010-05-28 10:21:18 EDT ---
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.
--- Additional comment from andre.edu on 2010-05-28 16:34:03 EDT ---
Confirmed - if I run s-c-n-tui and immediately select "Save&Quit", it doesn't create the file. Interesting.
--- Additional comment from dcantrell on 2010-06-11 14:17:09 EDT ---
*** Bug 598764 has been marked as a duplicate of this bug. ***
--- Additional comment from jpopelka on 2010-06-16 12:28:10 EDT ---
Fixed upstream (commit f6d58b7).
Comment 1RHEL Program Management
2010-06-22 14:13:01 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 3Alexander Todorov
2010-08-24 09:13:29 UTC
In latest snap #12 there's only system-config-network-tui, not the GUI part.