GNOME night light does not work after automatic login

Merry Christmas, everybody! :partying_face:

I have a touble with the GNOME night light,please help, thanks!

Distribution and version

Fedora 35 Workstation x86_64

Desktop environment and version

GNOME Shell 41.2

Session type

Wayland

Hardware spec

GPU: AMD Radeon RX 580 8G
CPU: AMD Ryzen 7 2700
Mobo: Gigabyte X470 AORUS ULTRA GAMING

Issue description:

When automatically logging into the GNOME desktop environment, the Night Light does not work.
(Change the color temperature, nothing changes.)
However, it works good after re-login with the password, and works fine in LiveCD.

Reproduction steps

  1. Activate night light through the settings
  2. Set user to auto-login
  3. Reboot

When you do automatic login what does the following show:
gsettings get org.gnome.settings-daemon.plugins.color night-light-enabled

gsettings get org.gnome.settings-daemon.plugins.color night-light-schedule-from

gsettings get org.gnome.settings-daemon.plugins.color night-light-schedule-to

gsettings get org.gnome.settings-daemon.plugins.color night-light-temperature

Is location services enabled for autologin?

Thanks

1 Like

Hi, Grumpey
Thank you for your reply.

Yes, the location services is enabled in settings.

~ $ gsettings get org.gnome.settings-daemon.plugins.color night-light-enabled
true

~ $ gsettings get org.gnome.settings-daemon.plugins.color night-light-schedule-from
12.0

~ $ gsettings get org.gnome.settings-daemon.plugins.color night-light-schedule-to
23.0

~ $ gsettings get org.gnome.settings-daemon.plugins.color night-light-temperature
uint32 2868

~ $ systemctl status geoclue
● geoclue.service - Location Lookup Service
     Loaded: loaded (/usr/lib/systemd/system/geoclue.service; static)
     Active: active (running) since Sun 2021-12-26 02:16:06 CST; 2s ago
   Main PID: 9762 (geoclue)
      Tasks: 5 (limit: 19071)
     Memory: 2.1M
        CPU: 50ms
     CGroup: /system.slice/geoclue.service
             └─9762 /usr/libexec/geoclue

Dec 26 02:16:06 ovo systemd[1]: Starting Location Lookup Service...
Dec 26 02:16:06 ovo systemd[1]: Started Location Lookup Service.

The night light still doesn’t work after create a new account.

I’d file a bug here

Thanks and Merry Christmas :slight_smile:

1 Like

I asked in the fedora group before and someone told me his night light was working fine,
So I’m not sure what caused the problem.

Thank you

I’ve moved the issue here:

2 Likes

Hi, maybe you could also check user session service (systemctl status --user name.service) related to night light:

systemctl status --user org.gnome.SettingsDaemon.Color.service

systemctl status --user org.gnome.SettingsDaemon.Color.target

systemctl status --user org.gnome.SettingsDaemon.Datetime.service

systemctl status --user org.gnome.SettingsDaemon.Datetime.target
1 Like

Hi,
I noticed switching to Xorg session and the night light works properly after reboot.

Wayland session

~ $ systemctl status --user org.gnome.SettingsDaemon.Color.service
● org.gnome.SettingsDaemon.Color.service - GNOME color management service
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Color.servi>
     Active: active (running) since Mon 2021-12-27 01:09:22 CST; 28min ago
   Main PID: 1270 (gsd-color)
      Tasks: 4 (limit: 19071)
     Memory: 9.3M
        CPU: 327ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/org.gn>
             └─1270 /usr/libexec/gsd-color

Dec 27 01:09:22 ovo systemd[949]: Starting GNOME color management service...
Dec 27 01:09:22 ovo systemd[949]: Started GNOME color management service.
~ $ systemctl status --user org.gnome.SettingsDaemon.Color.target
● org.gnome.SettingsDaemon.Color.target - GNOME color management target
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Color.target; static)
     Active: active since Mon 2021-12-27 01:09:22 CST; 28min ago

Dec 27 01:09:22 ovo systemd[949]: Reached target GNOME color management target.
~ $ systemctl status --user org.gnome.SettingsDaemon.Datetime.service
● org.gnome.SettingsDaemon.Datetime.service - GNOME date & time service
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Datetime.service; static)
     Active: active (running) since Mon 2021-12-27 01:09:22 CST; 28min ago
   Main PID: 1273 (gsd-datetime)
      Tasks: 4 (limit: 19071)
     Memory: 2.9M
        CPU: 39ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.SettingsDaemon.Datetime.service
             └─1273 /usr/libexec/gsd-datetime

Dec 27 01:09:22 ovo systemd[949]: Starting GNOME date & time service...
Dec 27 01:09:22 ovo systemd[949]: Started GNOME date & time service.
~ $ systemctl status --user org.gnome.SettingsDaemon.Datetime.target
● org.gnome.SettingsDaemon.Datetime.target - GNOME date & time target
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Datetime.target; static)
     Active: active since Mon 2021-12-27 01:09:22 CST; 28min ago

Dec 27 01:09:22 ovo systemd[949]: Reached target GNOME date & time target.

Xorg session

~ $ systemctl status --user org.gnome.SettingsDaemon.Color.service
● org.gnome.SettingsDaemon.Color.service - GNOME color management service
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Color.service; static)
     Active: active (running) since Mon 2021-12-27 01:40:30 CST; 1min 2s ago
   Main PID: 1364 (gsd-color)
      Tasks: 4 (limit: 19071)
     Memory: 8.4M
        CPU: 237ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.SettingsDaemon.Color.service
             └─1364 /usr/libexec/gsd-color

Dec 27 01:40:30 ovo systemd[943]: Starting GNOME color management service...
Dec 27 01:40:30 ovo systemd[943]: Started GNOME color management service.
Dec 27 01:40:30 ovo gsd-color[1364]: cd_client_find_device_by_property: assertion 'priv->proxy != NULL' failed
Dec 27 01:40:30 ovo gsd-color[1364]: could not find device: property match 'XRANDR_name'='DP-1' does not exist
Dec 27 01:40:30 ovo gsd-color[1364]: could not find device: property match 'XRANDR_name'='DP-1' does not exist
Dec 27 01:40:36 ovo gsd-color[1364]: Failed to connect to GeoClue2 service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: 'gnome-color-panel' disallowed, no agent for UID 1000
~ $ systemctl status --user org.gnome.SettingsDaemon.Color.target
● org.gnome.SettingsDaemon.Color.target - GNOME color management target
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Color.target; static)
     Active: active since Mon 2021-12-27 01:40:30 CST; 2min 4s ago

Dec 27 01:40:30 ovo systemd[943]: Reached target GNOME color management target.
~ $ systemctl status --user org.gnome.SettingsDaemon.Datetime.service
● org.gnome.SettingsDaemon.Datetime.service - GNOME date & time service
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Datetime.service; static)
     Active: active (running) since Mon 2021-12-27 01:40:30 CST; 3min 20s ago
   Main PID: 1371 (gsd-datetime)
      Tasks: 4 (limit: 19071)
     Memory: 2.9M
        CPU: 31ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/org.gnome.SettingsDaemon.Datetime.service
             └─1371 /usr/libexec/gsd-datetime

Dec 27 01:40:30 ovo systemd[943]: Starting GNOME date & time service...
Dec 27 01:40:30 ovo systemd[943]: Started GNOME date & time service.
~ $ systemctl status --user org.gnome.SettingsDaemon.Datetime.target
● org.gnome.SettingsDaemon.Datetime.target - GNOME date & time target
     Loaded: loaded (/usr/lib/systemd/user/org.gnome.SettingsDaemon.Datetime.target; static)
     Active: active since Mon 2021-12-27 01:40:30 CST; 3min 45s ago

Dec 27 01:40:30 ovo systemd[943]: Reached target GNOME date & time target.

Thank you!

1 Like

I found that mutter is related to this problem and replacing mutter-42.1-2.fc36.x86_64 with mutter-42.0-6.fc36.x86_64.rpm which is in fedora base packages, solved problem.