After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764390 - rfkill: restore last state instead of enabling both bluetooth and wifi when ending flight mode
rfkill: restore last state instead of enabling both bluetooth and wifi when e...
Status: RESOLVED DUPLICATE of bug 761051
Product: gnome-settings-daemon
Classification: Core
Component: rfkill
3.20.x
Other All
: Normal normal
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2016-03-30 19:52 UTC by Christian Stadelmann
Modified: 2017-06-12 22:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Stadelmann 2016-03-30 19:52:28 UTC 
Steps to reproduce:
1. make sure only wifi is enabled, but bluetooth is not
2. hit the rfkill button. Now both wifi and bt are disabled, gnome-shell shows flight mode
3. hit rfkill button again.

What happens:
Both bluetooth and wifi get activated

What should happen:
Only wifi should be on, bluetooth should be off.

Affected version:
gnome-settings-daemon-3.20.0-1.fc24.x86_64
gnome-shell-3.20.0-1.fc24.x86_64

Additional info:
I'd expect rfkill to restore the state before entering flight mode instead of enabling both. This is especially useful since some wireless features are not used at all on some mobile devices. I have bluetooth enabled about once a year on my laptop.

Note: there is no bugzilla component "rfkill" yet, so I'm putting this in the "general" component.
Comment 1 Bastien Nocera 2016-04-14 14:53:46 UTC 
Moving to rfkill component.
Comment 2 Juraj Fiala 2016-10-12 18:44:05 UTC 
This would be really nice to see, I keep disabling my bluetooth.
Comment 3 Benjamin Berg 2017-06-12 22:10:35 UTC 

*** This bug has been marked as a duplicate of bug 761051 ***