You are not logged in.
Ever since Gnome 43 came out, the night light feature hasn't been working for me. I know that Mutter 43 had a bug that made night light unavailable, but I've since updated to 43.1 and now night light says it's active but has no effect. I've also found that night light has issues with Nvidia GPUs, but I have an AMD GPU so that's not the cause either. Has anyone else had this issue?
The only suspicious thing I can find in my logs is that the Gnome color management service immediately loses its dbus name after acquiring it. I'm not sure if this is actually an issue, though, because D-Spy lists org.gnome.SettingsDaemon.Color in the session bus names. Here is systemd log for org.gnome.SettingsDaemon.Color.service:
Nov 14 19:20:41 arch systemd[883]: Starting GNOME color management service...
Nov 14 19:20:43 arch gsd-color[1266]: watch_fast: "/org/gnome/settings-daemon/plugins/color/" (establishing: 0, active: 0)
Nov 14 19:20:43 arch gsd-color[1266]: watch_fast: "/org/gnome/settings-daemon/plugins/color/" (establishing: 1, active: 0)
Nov 14 19:20:43 arch gsd-color[1266]: watch_fast: "/org/gnome/system/location/" (establishing: 0, active: 0)
Nov 14 19:20:43 arch gsd-color[1266]: watch_established: "/org/gnome/settings-daemon/plugins/color/" (establishing: 2)
Nov 14 19:20:43 arch gsd-color[1266]: watch_established: "/org/gnome/system/location/" (establishing: 1)
Nov 14 19:20:43 arch gsd-color[1266]: unsetenv() is not thread-safe and should not be used after threads are created
Nov 14 19:20:43 arch gsd-color[1266]: Starting color manager
Nov 14 19:20:43 arch gsd-color[1266]: fractional day = 19.345, limits = 20.000->7.000
Nov 14 19:20:43 arch gsd-color[1266]: night light mode on, using temperature of 4842K (aiming for 1700K)
Nov 14 19:20:43 arch gsd-color[1266]: bus_acquired_cb: acquired bus 0x55b51ae340c0 for name org.gnome.SettingsDaemon.Color
Nov 14 19:20:43 arch systemd[883]: Started GNOME color management service.
Nov 14 19:20:43 arch gsd-color[1266]: name_acquired_cb: acquired name org.gnome.SettingsDaemon.Color on bus 0x55b51ae340c0
Nov 14 19:20:43 arch gsd-color[1266]: name_lost_cb: lost name org.gnome.SettingsDaemon.Color on bus 0x55b51ae340c0
Nov 14 19:20:43 arch gsd-color[1266]: Registered client at path /org/gnome/SessionManager/Client17
Nov 14 19:21:06 arch gsd-color[1266]: fractional day = 19.352, limits = 20.000->7.000
Nov 14 19:21:06 arch gsd-color[1266]: night light mode on, using temperature of 4812K (aiming for 1700K)
Nov 14 19:22:06 arch gsd-color[1266]: fractional day = 19.368, limits = 20.000->7.000If I use dbus-monitor, I can see the display temperature property changing:
signal time=1668472439.512304 sender=:1.53 -> destination=(null destination) serial=330 path=/org/gnome/SettingsDaemon/Color; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.gnome.SettingsDaemon.Color"
array [
dict entry(
string "Temperature"
variant uint32 4816
)
]
array [
]I also found a script that uses the org.gnome.Mutter.DisplayConfig Dbus interface to set the gamma of a display, and that works fine. It's just night light that's not working.
Is there anything else I should check/try on my end? Thanks!
Edit: The solution to this issue was to go to the color section of Gnome's settings and enable color management for all my monitors. Doing this immediately changed the color temperature of my monitors. If I turn it back off, they get stuck at whatever temperature they are currently at, even if I later go and turn off night light.
Last edited by UnusuallyRegular (2022-11-21 02:46:50)
Offline
Thank you Internet stranger. This bugged me on Fedora 37 from the beginning, applying color profile to monitor fixed it immediately.
Offline