This bug seems to have been partially fixed at some point. The wireless kill switch now disables wireless networking /eventually/. However, it response seems extremely slow. For example if I boot with the wireless switch in the off position, wireless networking will not be disabled until well after the system has associated with an access point. So it is technically working. The more common reasons for using the switch are things like a) not wanting to connect to random insecure access points or b) disabling wireless on flights or other places where it is prohibited. It is still broken from a more practical point of view.
Given the above this may not or no longer be a kernel bug, but I'll provide the info below anyway and let the experts decide that kind of thing. Leann Ogasawara wrote: > Hi Jason, > > Per the kernel team's bug policy, can you please attach the following > information. Please be sure to attach each file as a separate > attachment. > > * cat /proc/version_signature > version.log Ubuntu 2.6.27-9.19-generic > * dmesg > dmesg.log attached > * sudo lspci -vvnn > lspci-vvnn.log > attached > It would be best to wait and catpure the dmesg output after you attempt > to flip your kill switch. I did the following: - boot with kill switch disabled (wireless "on") - enable kill switch - login - wait until associated with access point - wait until wireless disabled - disable kill switch - wait until wireless enabled and associated with access point - dmesh ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/21266068/dmesg.log ** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/21266069/lspci-vvnn.log -- wireless switch no longer disables WiFi https://bugs.launchpad.net/bugs/288886 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
