Night light does not work after resume from suspend or unlock.

[Hrishikesh Barua]

The night light feature does not work in these cases
 * Computer's screen shuts off due to timeout, and then is reactivated.
 * Computer is brought back from suspend
 * Computer desktop is locked, and unlocked using the password

In all these cases, the night light icon is present in the notification area, and it says "Night Light On". But the screen temperature is that of normal daylight.

In all these cases, disabling and re-enabling the night light using the notification area icon reactivates the night light.

Version information

Gnome desktop on Ubuntu 4.13.0-36.40-generic 4.13.13

4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

17.10 Artful Aardvark

Hardware : MSI GP62 QE - with i5-6300HQ, using the Intel graphics driver.
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: talonx 2732 F...m pulseaudio
 /dev/snd/controlC0: talonx 2732 F.... pulseaudio
CurrentDesktop: GNOME-Classic:GNOME
DistroRelease: Ubuntu 17.10
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=7808c7a8-dd4d-41e7-a2f2-032701229a6a
InstallationDate: Installed on 2016-05-05 (659 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Micro-Star International Co., Ltd. GP62 6QE
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=70280d26-8667-4d1b-9bbd-683373c14707 ro priority=low quiet splash acpi_osi= i8042.nomux=1 i8042.reset i8042.nopnp i8042.noloop usbcore.autosuspend=-1 vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-36-generic N/A
 linux-backports-modules-4.13.0-36-generic N/A
 linux-firmware 1.169.3
Tags: artful
Uname: Linux 4.13.0-36-generic x86_64
UpgradeStatus: Upgraded to artful on 2017-11-02 (114 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/25/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16J5IMS.113
dmi.board.asset.tag: Default string
dmi.board.name: MS-16J5
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.A
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16J5IMS.113:bd04/25/2016:svnMicro-StarInternationalCo.,Ltd.:pnGP626QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16J5:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
dmi.product.name: GP62 6QE
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1752680

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Hrishikesh Barua (talonx)]

These log files collect private information like the contents of my drives, which is not acceptable. I cannot run the apport-collect command.

[Daniel van Vugt (vanvugt)]

See also bug 1728342

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Hrishikesh Barua (talonx)]

The problem still exists in the latest (18.04.1) LTS release.

Output of /etc/lsb-release

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Marcin (mwoz123)]

I've related issue. I'm on Focal 20.04 LTS.

I did suspend my pc at night when night light was on,
Resumed (from suspend) next day in the afternoon when night light should be off but it still has much more red temperature color than it should (night light is on).

Event though I switch to disable night light nothing happens it still have too much red.
After couple suspends and resumes night light is still on no matter if it's a day or night.

It seems it only applies night light changes at time of planned toggle night and day light.

@vanvugt - can it stay here or I should extract it to new bug?

[Daniel van Vugt (vanvugt)]

Sounds like a different bug, maybe? This bug looks more like night light going off when it should be on.

Though I also notice the upstream developers are planning on moving the functionality out of gnome-settings-daemon and into mutter, which makes sense to me... The problem right now is that everything about monitors is managed by mutter _except_ for colour profiles (which I assume includes night light). So it may become confused as those multiple separate processes try to manage the same display hardware. gnome-settings-daemon sets a colour profile or night light, and then mutter turns the screen off and on according to power management. So the former colour profile setting might get forgotten.

https://gitlab.gnome.org/GNOME/mutter/-/issues/1283

[Rutvik Bhimani (rvbhimani)]

I've the same issue facing on Ubuntu 22.04.1 LTS x86_64.

I have a graphic driver Intel TigerLake-LP GT2 [Iris Xe Graphics]