Bug 1582743

Summary: Cannot set Automatic Sunset to Sunrise Night Light times
Product: [Fedora] Fedora Reporter: Andrea <mariofutire>
Component: gnome-settings-daemonAssignee: Rui Matos <tiagomatos>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 28CC: fmuellner, klember, mail, mkasik, ofourdan, rstrode, tiagomatos, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-28 23:25:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Missing times example none

Description Andrea 2018-05-26 16:14:04 UTC
Created attachment 1442007 [details]
Missing times example

Description of problem:

When I set Night Light based on Sunset Sunrise, both times are set to 00:00

Version-Release number of selected component (if applicable):

Fedora 28 fully updated, Gnome 3.28.2 Wayland

How reproducible:

Always

Steps to Reproduce:
1. Open Settings -> Devices -> Display -> Night Light
2. Night Light ON
3. Sunset to Sunrise
4. No times are shown

Actual results:

4. No times are shown

Expected results:

4. Sunset time and sunrise time

Additional info:

Manual times work

Comment 1 Andrea 2018-11-18 18:48:59 UTC
If anybody gets here,

it needs the location services to get sunrise and sunset.

It should really inform you that this is the problem, or let you override if you do not want to enable location services.

Applies to F29 as well.

I think it is still a bug.

Comment 2 Michael Yartys 2018-12-04 15:02:35 UTC
I experience the same problem on Fedora 29 and the latest GNOME version: 3.30.2

Andrea's suggested solution worked for me, and I do agree that this is a bug.

Comment 3 Ben Cotton 2019-05-02 20:10:51 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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' of '28'.

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 28 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.

Comment 4 Ben Cotton 2019-05-28 23:25:13 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.