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 787281 - Switching off airplane mode activates bluetooth (and some other issues)
Switching off airplane mode activates bluetooth (and some other issues)
Status: RESOLVED DUPLICATE of bug 761051
Product: gnome-shell
Classification: Core
Component: system-status
3.24.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-09-05 00:02 UTC by Frank
Modified: 2017-09-05 00:16 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Frank 2017-09-05 00:02:59 UTC
When I switch off first bluetooth and then WiFi, I get into the airplane mode. But when I open the system settings area, then I see the possibility to deactivate the airplane mode – this however activates my bluetooth…?!

So:
• The airplane mode should only be deactivatable by pushing the button on the keyboard and then restore the previous setting (what isn’t done right now, because always just bluetooth is activated instead).
• Airplane mode shouldn’t be deactivatable in the system status area menu, because this is just the result of every radio being off. Instead, both WiFi and bluetooth should be displayed for being turned on separately. Currently, just the WiFi settings are shown when being in airplane mode.
• When I first switch off WiFi and then bluetooth, the airplane settings aren’t shown in the system status area menu – this is just shown if I switch the radios off vice versa.
• The bluetooth settings aren’t shown when being in the airplane mode, generally.
Comment 1 Florian Müllner 2017-09-05 00:16:59 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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