Red Hat Bugzilla – Bug 1029686
When wireless is disabled, system goes into airplane mode
Last modified: 2015-06-29 08:53:41 EDT
Description of problem:
This is the opposite of bugs I have found while googling for work-around. When I turn off the wireless(or system boots up with wireless disabled) system goes to airplane mode.
Note that I also have a ethernet connection which should be connected but goes down with airplane mode.
Version-Release number of selected component (if applicable):
Turn on the system with wifi disabled and ethernet enabled.
Turn off the wifi while working from Networkmanager settings.
System goes to airplane mode disabling ethernet
System does not go to airplane mode, because other devices are acitve.
F20 - switching between wireless and wired.
If I disable the wireless (with wired not connected), airplane mode comes on.
If I switch from wireless -> wired
* wireless is disabled
* airplane mode comes on
* networks settings option is removed from menu
If you want me to test sequences ... fire away.
Created attachment 857101 [details]
video of network icon
I use wireless at home, wired at the office.
I always cold boot, never resume.
At home, connects fine.
At work, the airplane mode is on, and, on occasion the "network" icon is blinking.
At work I have this ritual:
* open settings
* open network
* turn off airplane
* turn off wireless
* turn on wired
The network icon is gone at this point.
System always comes up in "wireless" mode.
Would be NICE if it you could set "work" or "home" and toggle.
(In reply to Amir Hedayaty from comment #0)
> Description of problem:
> This is the opposite of bugs I have found while googling for work-around.
> When I turn off the wireless(or system boots up with wireless disabled)
> system goes to airplane mode.
> Note that I also have a ethernet connection which should be connected but
> goes down with airplane mode.
Can you post 'journalctl -b' output from just before, during, and after you turn of wireless, so we can see what is happening when the system goes into airplane mode? Turning off wireless *is* turning wifi airplane mode on, but that should not affect wired networking at all.
However, some laptops have BIOS functions that turn off all networking in "airplane" mode, so you might poke around in BIOS to see if that is the case with your model, and turn that off. I know some Dell Latitude laptops can do this.
Created attachment 858641 [details]
1. wiredON wirelessOFF airplaneOFF
Created attachment 858642 [details]
2. wiredON wirelessON airplaneOFF
Created attachment 858643 [details]
3. wiredON wirelessOFF airplaneOFF
Created attachment 858644 [details]
4. wiredOFF wirelessOFF airplaneON
Created attachment 858645 [details]
5. wiredOFF wirelessOFF airplaneOFF
Created attachment 858646 [details]
6. wiredON wirelessOFF airplaneOFF
I assumed that making changes without rebooting would be OK. If not, send me instructions detailing exactly what you need.
Ah, (In reply to Brent R Brian from comment #1)
> F20 - switching between wireless and wired.
> If I disable the wireless (with wired not connected), airplane mode comes on.
> If I switch from wireless -> wired
> * wireless is disabled
> * airplane mode comes on
> * networks settings option is removed from menu
> If you want me to test sequences ... fire away.
Which process are you using to "disable the wireless"? Are you choosing "turn off" from the Wi-Fi section of the GNOME Shell network status icon?
In this case, yes, the network settings menu was used.
Created attachment 892882 [details]
journal -b as requested ... if not right, ping me
The symantecs of this fault are important to explain.
I've got a 'newish' Dell Latitude 6340 laptop - with the Wifi On/Off switch. Putting the switch into the Off position - does what it is meant to - ie switches off the wireless (correct). The most annoying things about this switch is that is it also disables the onboard hardwired ethernet port at the same time - or more clearly - it seems to cause the port to go ethdown. You can re-enable it easily enough by manually selecting the port from the menu dropdown [top right] in Gnome3.
I will find a bluetooth dongle and try and see if that starts/stop when the wireless enable/disable switch is toggled and add more to this fault when I've done this.
Fedora 21 x86_64 Workstation edition
(In reply to Max E from comment #14)
> The symantecs of this fault are important to explain.
> I've got a 'newish' Dell Latitude 6340 laptop - with the Wifi On/Off switch.
> Putting the switch into the Off position - does what it is meant to - ie
> switches off the wireless (correct). The most annoying things about this
> switch is that is it also disables the onboard hardwired ethernet port at
> the same time - or more clearly - it seems to cause the port to go ethdown.
> You can re-enable it easily enough by manually selecting the port from the
> menu dropdown [top right] in Gnome3.
Dell laptops seem to have tendency to power off Wi-Fi when ethernet is on and vice versa.
Can you look into BIOS and found out what can be set/changed there.
Also, toggle the hardware switch and check what it causes, by getting output of commands like:
$ rfkill list
$ ip addr
I did actually find that the WWLAN controller when ethernet is plugged in - was switched OFF. I have now switched this on....Lets see if that makes a difference.
As requested, a number of output files from my laptop as requested. dmesg,rfkill list and ip addr - outputs with Wireless LAN hardware disable on [ie wireless disabled] and hardware disable off [ie wireless working].
Created attachment 1029524 [details]
dmesg with wifi on and working
Created attachment 1029525 [details]
dmesg with wifi off and disabled [hardware switch]
Created attachment 1029527 [details]
IP Address showing no connections - wifi hardware disabled
Created attachment 1029528 [details]
IP Address showing connections - wifi hardware enabled
Created attachment 1029529 [details]
rfkill list output with wifi switch disabled
Created attachment 1029530 [details]
rfkill list output with wifi switch on and enabled
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Thank you for reporting this bug and we are sorry it could not be fixed.