+++ This bug was initially created as a clone of Bug #1464360 +++ Description of problem: My hardware is a Lenovo x260 (Skylake i7 with Intel HD520 GPU) Version-Release number of selected component (if applicable): gnome-shell-3.24.2-1.fc26.x86_64 How reproducible: 100% Steps to Reproduce: 1. Log in using Gnome on xorg instead of wayland 2. Turn on night light 3. Wait until night light time has activated 4. See night light enabled icon but notice no change in screen colour Actual results: No change in screen colour on primary or secondary screens Expected results: Change in screen colour as observed in Wayland Additional info: --- Additional comment from Florian Müllner on 2017-06-23 08:51:58 EDT --- It's expected to work on X11 as well (and does here). In any case, gnome-shell only exposes the feature in the system menu, the actual functionality is implemented in gnome-settings-daemon's color plugin. --- Additional comment from Andrew Stiegmann on 2017-07-11 20:20:03 EDT --- Works for me on Fedora 26 on XOrg. Initially thought it was not functional but verified using manual mode. Try that and see if that does the trick. --- Additional comment from Andrew Hutchings on 2017-07-12 03:55:58 EDT --- Nope, not working in manual mode on the laptop's screen or external monitor. My journal gets sprayed with this though when I try: Jul 12 08:53:40 lxj-x260.local gsd-color[1803]: could not find device: property match 'XRANDR_name'='DP-1' does not exist Jul 12 08:53:40 lxj-x260.local gsd-color[1803]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist --- Additional comment from Andrew Stiegmann on 2017-07-12 17:44:17 EDT --- Might be helpful if you upload the output of xrandr and the relevant journalctl entries to this bug. Might be a clue in there as to what is happening. --- Additional comment from Andrew Hutchings on 2017-07-12 18:28:25 EDT --- I started having tons of other Xrandr based issues including hangs and corruptions with multiple monitors recently too. This has been a F26 system since before the beta so must have picked up some bad config along the way, I've replaced the OS on it with something else as I needed it in production today. Not sure I'll get a chance to debug more soon. I don't have the problem on any of my other Fedora machines. I'll close as !bug. Sorry for wasting time. --- Additional comment from Grant on 2017-09-05 02:24:00 EDT --- I also have problems with night light not working in Fedora 26 fully updated as of today. Redshift is now broken also. Redshift worked fine on this i7 laptop when running Fedora 25. I am using multi monitor, but with single monitor attached, still getting problem. This is a show stopper for me because I work at night and must have this feature. I sometimes get a strange hardware error message on the windows display after dnf upgrade; and always on shutdown, but I don't know how to retrieve it/them, and everything seems to work. Getting this error on /var/log/messages: could not find device: property match 'XRANDR_name'='DP-1' does not exist
mcelog is installed, but "problem reporting" says it was not used. So maybe it is not set to load at startup, but I never touched it so it should be default installation. I do get ACPI warnings and UEFI unable to update warnings/errors.
Created attachment 1322101 [details] dmesg and more from the message log.
Comment on attachment 1322101 [details] dmesg and more from the message log. there are also many semaphore errors as the system shutsdown but I don't see them in here in "messages" file.
Created attachment 1322103 [details] message file after trying to run redshift
Created attachment 1322104 [details] messages after turning off "night light" and then turning it back on. It booted with it on.
Created attachment 1322382 [details] fresh install, same problem, dmesg in full.
Created attachment 1322384 [details] fresh install, same problem, journalctl in full.
Did a fresh install of current ISO v26-1-5, no multiple monitors on Toshiba i7 Haswell laptop. Some problem with night light (and hardware errors not captured by mcelog) I turn it on an off several times and then sent you the dmesg and journalctl in full. Ubuntu 17.04 redshift works on this hardware (not that I want to run at OS :)
Night light just stopped working for me since last week, too. Maybe a GNOME upstream bug? See these recent reports: https://bugzilla.gnome.org/show_bug.cgi?id=780167
(In reply to Gergely Gombos from comment #9) > Night light just stopped working for me since last week, too. Maybe a GNOME > upstream bug? See these recent reports: > https://bugzilla.gnome.org/show_bug.cgi?id=780167 Incidentally, redshift is working properly so the problem is definitely not with my screen.
Journalctl: nov 07 20:28:38 fedora-laptop gsd-color[2201]: could not find device: property match 'XRANDR_name'='DP-1' does not exist nov 07 20:28:38 fedora-laptop gsd-color[2201]: could not find device: property match 'XRANDR_name'='eDP-1' does not exist Maybe similar to https://bugzilla.redhat.com/show_bug.cgi?id=1464360?
This bug got fixed for me after upgrading to F27. Now night light is working properly.
@Gergely, thanks for posting. nice to hear!
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.