Bug 1461239
Summary: | Fedora 25, 26, and 27 always think airplane mode is enabled on Atheros AR5212/Lenovo R61 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | wallyk <wallykramer> |
Component: | network-manager-applet | Assignee: | Lubomir Rintel <lkundrak> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 27 | CC: | blueowl, dcbw, emailtoflorian, lkundrak, thaller |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-11-30 18:41:53 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
wallyk
2017-06-14 02:50:19 UTC
Hard blocked: yes this is usually controlled by your hardware. Usually you would need to press some "Fn" key. Some laptops have a physical switch, but since your issue depends on the Fedora version, that's obviously not the case. I wouldn't expect that the hardware block is even set by software. So, it's surpising that it depends on the Fedora version. Doesn't sound like a NetworkManager problem. Certainly not of applet. What happens if you run a `rfkill unblock all` ? The command `rfkill unblock all` runs silently, but no change in airplane mode, and the output of `rfkill list` still shows `hard blocked: yes`. @Thomas: On the Lenovo R61, there is a keyboard icon with a laptop emitting radiation out both sides. (Could double as speakers on/off I suppose.) When I press Fn+F5, Fedora temporarily displays a "status window" (similar to battery status, brightness change, or select monitor) with an aircraft icon and text "Hardware Airplane M...". Since the window is fleeting and not part of the X GUI, I can't grab it, resize, it, or screen capture it. But there is no discernible effect nor message in `dmesg`. The wifi hardware details (via lshw) are: *-network description: Wireless interface product: AR5212 802.11abg NIC vendor: Qualcomm Atheros physical id: 0 bus info: pci@0000:03:00.0 logical name: wls3 version: 01 serial: 00:1d:d9:3f:b8:c7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath5k driverversion=4.11.10-100.fc24.x86_64 firmware=N/A ip=192.168.1.3 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:17 memory:df3f0000-df3fffff First noticed the problem after upgrading to Fedora 25. Worked hard to find a fix or workaround, but eventually did the painful reinstall of F24 to have a functional laptop. Details at https://ask.fedoraproject.org/en/question/97479/fedora-25-always-thinks-airplane-mode-is-enabled/ Since then I have tried "live" Fedora with editions 25, 26, and 27 including some alphas and betas. Conclusion: some change present beginning in F25 does not correctly sense the "airplane mode" hardware setting. It seems to be looking at the wrong bit because changing the hardware switch and/or toggling the keyboard Fn+F5 setting does not affect the its opinion of airplane mode. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 EOL if it remains open with a Fedora 'version' of '27'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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 this bug is closed as described in the policy above. 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. |