Bug 1187954
| Summary: | network manager always in airplane mode | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin Sebor <msebor> | ||||||||
| Component: | control-center | Assignee: | Control Center Maintainer <control-center-maint> | ||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 21 | CC: | control-center-maint, dcbw, fmuellner, jklimes, mkasik, msebor, ofourdan, oholy, psimerda, rstrode, steeve.mccauley, tiagomatos | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-12-02 08:22:10 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: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Martin Sebor
2015-01-31 18:36:01 UTC
I not sure if I understand correctly what is your issue. Can you explain it once more? And how do you toggle wireless, via Gnome network icon? Turning off wireless means turning wifi to airplane mode. Anyway, please grab NetworkManager logs containing your actions so that we can see what happened? # journalctl -b -u NetworkManager What computer and Wi-Fi card do you have? Created attachment 986854 [details]
NetworkManager log.
Sorry if I wasn't clear. Let me try again. I normally use only my wired connection and my wireless is always turned off, which is what I discovered leads to the Airplane Mode turning on. As an experiment, after turning off Airplane Mode (via the drop-down menu at the airplane icon in the top right corner of the GNOME desktop) I turned on my wireless (again via the same menu), and then turned it back off. That turned Airplane Mode back on. I've read somewhere that Airplane Mode disables some connectivity functions. I don't know what functions it might disable but since I'm connected to the network I don't want any connectivity functions disabled. I should also note that this is on my workstation, not my laptop. My (admittedly limited) understanding of Airplane Mode is that it's primarily (only?) useful on mobile devices where there's a concern with the WiFi radio potentially interfering with airplane communications signals. Since this a stationary workstation, there is no such concern, and there should be no need for the Airplane Mode to ever turn on. The Network Manager log is attached. Same issue here, I have wired network connection on desktop, with wifi disabled and when I first login the "Airplane Mode" is always enabled. I can turn it off in the main gnome shell menu but Airplane Mode on a desktop doesn't seem entirely necessary, even if it is an all-in-one ;) I'm now running Fedora 22. Created attachment 1043716 [details]
Fedora 22 NetworkManager log
"Airplane Mode" should stop the computer to transmit over wireless, which usually means to disable Wi-Fi and bluetooth. It works fine for me, when I test with Fedora 22, Gnome 3 on Lenovo T400. Toggling Wi-Fi in Gnome doesn't change "Airplane Mode" switch for me. Maybe you don't have bluetooth present and then both the Wi-Fi switch and "Airplane Mode" actually controls Wi-Fi. Anyway, re-assigning to Gnome Control Center. Created attachment 1044322 [details]
Toggling Wi-Fi/airplane switches and dispalying 'rfkill list' on T400 (Fedora 22)
I don't have bluetooth on this desktop. Toggling Wi-Fi has no effect on the appearance of the "Airplane Mode" menu entry, which only appears after a reboot. Wired: enabled Wifi: disabled Bluetooth: no This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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. FYI, I still see this issue in F22. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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. |