Description of problem:
A typical scenario: use laptop with internal screen while or after night light has been enabled. Close lid to put to sleep. Then, next morning (after night light off time) put laptop on the docking station and wake up with external monitor. Nightlight then stays enabled on the external screen.
In fact, the night light should be turned off on any screen at that time.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Run laptop on internal screen with night light enabled
2. Put laptop to sleep
3. Wake on docking station with external monitor at a time when night light is supposed to be turned off.
Night light stays on on external screen.
Night light should be turned off.
This is on a Thinkpad T450S with Intel graphics.
A workaround is to select "Logout" from the menu. This darkens the screen triggering night light to be turned off. Simply cancelling the logout is sufficient, the night light then stays off.
It seems that there is some state check missing or a timed job to be executed at or after night light off time before going to sleep with night light enabled.
This might actually be a general problem according to https://bugzilla.gnome.org/show_bug.cgi?id=786569
This is still a problem on F28. Can some maintainer please have a look soonish. It's broken for more than half a year now.
(In reply to Tim Niemueller from comment #2)
> Can some maintainer please have a look soonish.
Thats not how it usually works ;)
Perhaps you can try the patch in the upstream bugreport and report if it fixes the issue there ?
(In reply to Yanko Kaneti from comment #3)
> Thats not how it usually works ;)
It never hurts to ask. A maintainer might have picked this up already.
> Perhaps you can try the patch in the upstream bugreport and report if it
> fixes the issue there ?
If the maintainer provides a build I'd happily do so. Unfortunately, I do not have the time to do this myself this time.
A scratch with the test patch applied
I have installed it. Will report back tomorrow if it worked :-)
It worked this morning. Great, thanks!
It worked a couple more times. Are you going to push this as a regular update?
I landed the patch upstream in g-s-d. So it will reach Fedora at the latest with the next stable release update to 3.28.2.
I am really surprised that the patch fixes this. But all the better :)
The issue just occurred again. It seems to be much better but not entirely fixed. Was the first time since installation a week ago.
Thanks for the feedback! I created the upstream issue
to track the remaining problems.
After two more days I have to say that it keeps being broken. Did work for a while, not doesn't for several days in a row. Any other idea or package to test?
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.
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
Thank you for reporting this bug and we are sorry it could not be fixed.