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 788714 - The automatic timezone control doesn't hint it needs location to be enabled
The automatic timezone control doesn't hint it needs location to be enabled
Status: RESOLVED FIXED
Product: gnome-control-center
Classification: Core
Component: Date and Time
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: Kalev Lember
Control-Center Maintainers
triaged
Depends on:
Blocks:
 
 
Reported: 2017-10-09 13:05 UTC by Sebastien Bacher
Modified: 2018-09-11 07:21 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Greys out automatic timezone if location is disabled in privacy, update comment to reflect the need to enable location (4.03 KB, patch)
2018-08-20 20:34 UTC, Petr Kubánek 		none Details | Review

Description Sebastien Bacher 2017-10-09 13:05:32 UTC 
The issue has confused some users on GNOME 3.26.1/Ubuntu, if you disable the access to the location service in the privacy panel and go to the date&time panel the "automatic timezone" setting is showed as active but doesn't work. 

The corresponding line has a subtext into that an internet connection is needed, it should maybe also hint that access to the location is needed or display a warning when the location service is disabled?
Comment 1 Daniel van Vugt 2018-01-10 07:02:01 UTC 
See also: https://launchpad.net/bugs/1741928
Comment 2 Petr Kubánek 2018-08-20 20:34:23 UTC 
Created attachment 373412 [details] [review]
Greys out automatic timezone if location is disabled in privacy, update comment to reflect the need to enable location
Comment 3 Petr Kubánek 2018-09-11 03:47:07 UTC 
Patch with software and text string change was merged to master, see https://gitlab.gnome.org/GNOME/gnome-control-center/merge_requests/165

Can someone please close this issue? Reopen if needed.