From Bugzilla Helper: User-Agent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko) Description of problem: When activating a network interface, one expects the status to change from inactive to active, yet in my case, this doesn't happen. It already didn't happen in FC1 and FC2, FC3-test1, -2 and -3, and now FC3. The interface in question is an isdn interface which is *not* activated at boot. Interestingly isdn services refuse to be started at boot, so that the isdn modules are only loaded once the user activates the interface for the first time after boot. Version-Release number of selected component (if applicable): 1.3.22-1 How reproducible: Always Steps to Reproduce: 1. click network device control to start application. Also works with the "Network" program of "System Settings" (is same program, but second choice is intended for root, only, IIUC) 2. click to activate a user-activateable network interface 3. Actual Results: see how the status column is not updated Expected Results: "inactive" changes to "active" Additional info:
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
This problem persisted in FC4 and still persists in FC5. It doesn't need to be fixed in FC3, but should be fixed in FC5 or at least fc6. Kind regards
thanks!
The problem persists in FC5 and FC6
Oops, correction: the problem only persists when activating an isdn interface, however, the eth interfaces are handled correctly.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp