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 765279 - Bluetooh and Wifi in Power Savins are Confusing
Bluetooh and Wifi in Power Savins are Confusing
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Power
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Richard Hughes
Control-Center Maintainers
triaged
Depends on:
Blocks:
 
 
Reported: 2016-04-20 00:07 UTC by Mikela
Modified: 2021-06-09 16:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Mikela 2016-04-20 00:07:01 UTC
Based on the location of the bluetooth and wireless off settings in the power settings section it implies those settings are for low power and not just for turning them on and off.

Since they can be turned off both in other parts of the settings area as well as in the top bar.
Comment 1 Leo Arias 2018-02-27 15:22:59 UTC
I think this is a very unfortunate design.

Yesterday I found that 5 minutes after I left my computer, the wi-fi was turned off so I couldn't keep connecting to it from my other machine.

I found this option on the gnome control center, which says:

Wi-Fi, Turn off Wi-Fi to save power.

It was enabled. So my thought was, if I disable it, then wi-fi will never be turned off to save power. I was surprised when I clicked it and my wi-fi was disabled immediately. Just the opposite from what I wanted, instead of keeping it on, it turned it off.

I don't see a reason to have this checkbox on the power section of the control panel. I can disable my wi-fi from the network section. What I would like is an option that lets me keep my wi-fi always on, even when the machine is idle.
Comment 2 Felipe Borges 2018-02-27 16:03:30 UTC
Alternatively, we could set NMSettingWirelessPowersave in there. Thoughts?
Comment 4 André Klapper 2021-06-09 16:24:27 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.