Created attachment 601471 [details] Proposed patch from Ubuntu Launchpad. Description of problem: There's a bug which prevents the Bluetooth and WiFi radio to operate independently of each other. Turning on/off either Bluetooth or WiFi would turn on/off the other interface. This happens when using the keyboard button (Fn+F2) and gnome-shell switches from the Bluetooth and Network applets. Version-Release number of selected component (if applicable): 3.4.6-3 How reproducible: Always Steps to Reproduce: 1. Press Fn+F2 to turn on or off the WiFi radio. 2. Observe that both Bluetooth and WiFi adapters turn on/off. Alternative Steps to Reproduce: 1. From within gnome-shell turn off Bluetooth from the indicator's menu. 2. Observe that both Bluetooth and WiFi adapters turn on/off. Actual results: Both Bluetooth and WiFi radios are turned on/off. Expected results: WiFi and Bluetooth radios should operate independently of one another.
I re-built a kernel RPM with the above patch and it seems to work so far.
The rfkill code for this driver has been removed entirely upstream. I think I'll just backport that, which would fix it for other laptops too.
Confirming that an unpatched 3.5.0 kernel† does not exhibit the issue. † Custom kernel package based on 3.5.0-2.fc17
F16 should be getting a rebase to 3.5 next week.
So, it is taking a little longer due to an issue seen in F17 with the 3.5 kernels. Once that is fixed, we will be pushing 3.5 to F16. Sorry for the delay, but it is still going to happen.
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.