@herf
Same problem here - last days Windows 10 Version 1903 came in, and since then f.lux doesn't work on this monitor.

Driver details as requested:

Intel Corporation 10.18.10.4358: Intel(R) HD Graphics (20151221) Fresco Logic 2.1.34054.0: Fresco Logic IDDCX Adapter (20171113) Citrix Systems Inc. 10.50.21.200: Citrix Indirect Display Adapter (20171107) Generic PnP Monitor, 432 x 324mm, built 2009 Chromaticities: R=0.639648 0.330078 G=0.299805 0.599609 B=0.150391 0.059570 W=0.313477 0.329102 sRGB gamut: 100%, AdobeRGB gamut: 64% Generic PnP Monitor, 432 x 324mm, built 2007 Chromaticities: R=0.639648 0.330078 G=0.299805 0.599609 B=0.150391 0.059570 W=0.313477 0.329102 sRGB gamut: 100%, AdobeRGB gamut: 64% Monitor 1 on Intel(R) HD Graphics: VCGT=0 gamma=1 Monitor 2 on Intel(R) HD Graphics: VCGT=0 gamma=1 Monitor 3 on Fresco Logic IDDCX Adapter: VCGT=0 gamma=1 Windows Build: 18362.836

Below is my driver info

Intel Corporation 10.18.10.3540: Intel(R) HD Graphics 4600 (20140330)
NVIDIA 26.21.14.4587: NVIDIA GeForce GTX 860M (20200403)

PnP-Monitor (Standard), 443 x 249mm, built 2010
Chromaticities:
R=0.639648 0.330078
G=0.299805 0.599609
B=0.150391 0.059570
W=0.313477 0.329102
sRGB gamut: 100%, AdobeRGB gamut: 64%

PnP-Monitor (Standard), 531 x 299mm, built 2010
Chromaticities:
R=0.632813 0.350586
G=0.334961 0.608398
B=0.144531 0.057617
W=0.313477 0.329102
sRGB gamut: 76%, AdobeRGB gamut: 54%

PnP-Monitor (Standard), 344 x 193mm, built 2013
Chromaticities:
R=0.565430 0.330078
G=0.323242 0.577148
B=0.160156 0.144531
W=0.313477 0.329102
sRGB gamut: 74%, AdobeRGB gamut: 48%

Monitor 1 on Intel(R) HD Graphics 4600: VCGT=0 gamma=1
Monitor 2 on Intel(R) HD Graphics 4600: VCGT=0 gamma=1

Windows Build: 9600

Intel Corporation 20.19.15.4300: Intel(R) HD Graphics 530 (20151001)
NVIDIA 26.21.14.4587: NVIDIA GeForce GTX 960M (20200403)

PnP-Monitor (Standard), 473 x 296mm, built 2011
Chromaticities:
R=0.644531 0.341797
G=0.308594 0.617188
B=0.151367 0.060547
W=0.313477 0.329102

sRGB gamut: 91%, AdobeRGB gamut: 64%

PnP-Monitor (Standard), 521 x 293mm, built 2013
Chromaticities:
R=0.640625 0.337891
G=0.315430 0.628906
B=0.159180 0.058594
W=0.313477 0.329102

sRGB gamut: 89%, AdobeRGB gamut: 63%

Windows Build: 19041

@einst3 said in classic f.lux earliest wake time:

ignore on 2. "or i close ui and reopen". still does not show wake time.

@ViwwiV did you figure this out? I'm having the same issue

20 yrs English teacher here. Essentially, yes to the grammar points above.

It appears to me we have an idiomatic problem (beyond the mere grammatical construct). But fundamentally there's a semantic problem which leads to surprise and frustration.

"Light is making your body earlier/later" is not idiomatic bc it doesn't work conceptually as these words are commonly used.

Light cannot make a human body. And it cannot prevent a human body from moving, so it cannot make a body later. Conversely, it also cannot propel it, so it cannot make a body earlier. Bodies are necessarily 'embodied' things. Light is not embodied.

Therefore, readers feel confusion bc the concepts can't interact in the way it is written..

From my reading, there's a conflation of concepts in the statements under question. Bodies have various clocks which can be adjusted differently. But the statement collapses the two concepts into a single word.

Bodies are not clocks, but have and use various clocks. Clocks can be set earlier or later, slowed, or sped up. There's a lot of variability with clocks. The concept of a body has a different set of variability.

Therefore, it would add clarity if the statement "... is making your body earlier/later" were changed. As a final note: the progressive form further adds to the confusion, too. In English, it's a terribly awkward form to begin with. Many writers just say to avoid it entirely, if possible.

Turn off Night Light.

I am speechless. That, wow, I don’t know, you would think that since Windows 10 has Night Light, Intel should have made sure this didn’t end up being a problem somehow. Nice work figuring it out!

@BlackLabs said in f.lux stops working exactly at 9 p.m.:

@TwoCables
Thanks for that tip - will try. I have the exact same problem with the original poster - right at 9 p.m. on the dot it starts to flicker. Didn't realize that f.lux and the Win10 "Night light" setting clashes with each other.

It's not a setting. It's two programs conflicting with each other because both are trying to do the same thing.