Description of problem: After installing F10-Beta and disabling NM, when configuring an ethernet device to be started at boot time with s-c-n, s-c-n doesn't change ONBOOT to yes in the various ifcfg-eth0 files. Version-Release number of selected component (if applicable): system-config-network-1.5.10-1.fc9.noarch How reproducible: Very Steps to Reproduce: 1. Select an ethernet device 2. Change "Activate device when computer starts" 3. Save settings Actual results: Expect ifcfg-eth0 to have ONBOOT modified Expected results: ONBOOT parameter is not modified. (In either direction) Additional info:
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle. Changing version to '10'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This should be fixed in the latest release of s-c-n. It should hit the testing repository soon.
Having the same problem. Each time I restart my PC, I need to go to system-config-network and enable the network device.....
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This is still a problem with F12. After a fresh install, I have no network configured. So I ran system-config-network, entered the appropriate details, and did "service network restart". The settings I'd entered were ignored because ifcfg-eth0 still had ONBOOT=no in it.
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
Aaarrrgghhhh!!! Sometimes I despair of the Red Hat bugzilla. Commenters are not allowed to update the version number. But that's OK, because I've been told that all you need to do to keep a bug open when a release goes EOL is to leave a comment saying it's still relevant to a newer release. So why is this one being closed? Just like seemingly every other bug that this happens to. So just for the record, THIS IS A PROBLEM WITH FEDORA 12. Please reopen it.
Doesn't work on Fedora 12 EITHER. In fact I no longer even see eth0, when I run the ifconfig command.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.