Description of problem: It gets stuck booting because the wifi is rfkilled on my HP Elitebook 6930p Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Reboot - this will disable wifi before it gets back to the BIOS (and the BIOS won't turn it back on) 2. It gets stuck at nm-online in one of the services. 3. when that times out, it gets the rfkill unblock all in rc.local that turns it on. Actual results: It waits preventing unblock Expected results: Either the kernel, the kernel module, or something would unblock the interfaces, OR network manager would start up and not wait for these optional interfaces or there would be an easy config to bypass them. Additional info:
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.