I'm having the exact same problem, and I've had it many months.

OS X El Capitan
Version 10.11.6

MacBook Pro (Retina, 13 inches, mid 2014)
Processor 2,8 GHz Intel Core i5
Memory 8 GB 1600 MHz DDR3
Graphics Intel Iris 1536 MB

YouTube fullscreen in Chrome 57.0.2987.133 (64-bit) is when it occurs.

Hope this can be fixed! Looks like it's been an issue for ~2 years..

still having this problem: https://forum.justgetflux.com/post/13522

here the picture links since embedding didn't work:

https://www.dropbox.com/s/f1mu1azacaohefp/Screenshot 2017-02-21 23.30.39.png?dl=0

https://www.dropbox.com/s/x3cyex5yr50e0ry/Screenshot 2017-02-21 23.32.06.png?dl=0

Also I haven't noticed the problem when playing a video file with VLC or similar -- just from streaming.

My 5cents, disabling the auto brightness adjustment didn't help my issue.
What helped in my case is that I replaced the cable of the monitor.

lightning to D-SUB adapter with a D-SUB cable connected to the monitor -> constant screen refreshing waving/flickering effect (strangely only when flux enabled and color is warm)

HDMI -> DVI cable connected to the monitor - No flickering

I tried with 2 different monitors and I had the same issue / effect / resolution one LG and one Samsung. (Simply changing the D-SUB cable to another D-SUB didn't help, using another Lightning socket or adapter didn't help either)

@joankim Sorry that we disappointed you I wish you well.

Had a crash this morning. Machine was up, I could SSH to it, but the screen was dark and flickering. Rebooted and checked the system.log. This may be a GPU failure issue, but I figured I would throw this in for those with similar errors and a LOT of Flux messages, but the more I dug the more it seemed like the issue was my GPU and not Flux.

Oct 25 08:04:05 max kernel[0]: IOVendorGLContext::ReportGPURestart Oct 25 11:49:04 max watchdogd[402]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Oct 25 11:49:05 max watchdogd[402]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer) Oct 25 11:05:10 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:05:35 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:21 --- last message repeated 1 time --- Oct 25 11:06:21 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:41 max kernel[0]: NVDA(OpenGL): Channel timeout! [... above repeated several times, then ... ] Oct 25 11:49:05 max Dock[360]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Google Chrome[333]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max GPGSuite_Updater[1355]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max CalNCService[383]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max SystemUIServer[362]: HIToolbox: received notification of WindowServer event port death. [... later, Flux repeating every few seconds ...] Oct 25 11:51:04 max Flux[951]: Empty gamma size Oct 25 11:51:04 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port

Early 2008 Mac Pro, 18GB RAM
OS X 10.11.6
NVIDIA GeForce 8800 GT 512 MB
F.lux 37.7

I've now updated my NVIDIA card with their drivers, maybe it is a GPU issue and not a Flux issue. Wait and see FTW!

@Tungsten_smooth said:

@Gentz Now you can open the magnifier and invert the colors (ctrl alt i). I think it's the APU not understanding the color inversion part.

Yeah, something somewhere is definitely not allowing f.lux to work correctly.

Thank you Elhem! I will give that a shot.

I'd like to have an option for flux to run on a per screen basis. I'd like my full screen games to be clear and colour accurate while youtube or anything on my second monitor is still easy on the eyes at night. If I disable flux for rocket league, then the other monitor is blinding while im playing. Also a lot of colour changes during alt tabs.

The issue with flickering when wake up the machine from Stand-by - issue still persists in even in the latest update.

When the flashing happens there is a log:

2015-08-14 1:42:47.991 AM Flux[589]: Display list confused, doing full reset.

I found a solution for my nvidia cards: Gnome 3.24 has a night mode included.
Only one color temperature, but it works.

Think this topics

This thread has been wonderful! Could we also dig up how much the chances are that offspring from adhd patents will have all this?

I have the Philips Hue color lights and I'm very happy with them so I thought I'd share how I have them set up with F.lux on my Windows desktop computer and my Amazon Echo in the event anyone reading this might benefit from it.

So I have the Philips Hue lights programmed to turn on automatically when the sun sets through an If This Then That recipe on www.IFTTT.com. The recipe works with the Weather Channel and it knows my location so once the sun sets, it then triggers the Philips Hue Channel to send instructions to my Philips Hue bridge, which turns on all the Philips Hue lights in my apartment. The color of the lights is the standard bright white that those lights emit if a color isn't chosen, but that's okay (for me) since it's just providing light when walking in the door.

Once inside, though, I turn on my Windows desktop computer and F.lux overrides the system and changes the color of the lights to what can only be described as a soothing yellow/orange glow much like that soothing glow of a Himalayan salt lamp. (I have no idea how it does this, but I'm very happy with it and it's very relaxing. And it even dims as the night progresses.)

The problem I encounter, though, is that I don't always have my computer on, so once the computer goes to sleep or turns off, the Hue lights then remain at that level of brightness until I change them or turn them off. It's not a big deal, but after reading this forum and learning that red light doesn't affect our circadian rhythm like blue and green does, I made another recipe on IFTTT recipe for a darkroom mode. The Amazon Alexa Channel listens for my trigger word, which is darkroom, and it instructs the Philips Hue Channel to change the color of all my lights to red. (The Philips Hue Channel allows you to name a color as well or use a CSS hex code. I tried a variety of them and settled on this one: #A00000.)

So now, about an hour before going to bed I tell my Amazon Echo: "Alexa, trigger darkroom." And she changes all the lights to red. I feel the difference just like someone else mentioned here about how it made them feel and that's now my nightly routine. But hopefully, once F.lux becomes fully functional I won't have to do this and it will just take care of it all.

@Charles-XII

We are really interested in the different ways that people sleep, and we are very aware that everyone is different. f.lux doesn't tell people when to go to bed, only when to begin dimming the lights.

Based on the literature, even biphasic sleepers are likely to need a strong light dark rhythm, because melatonin release and uptake happens over a ~24 hour rhythm, regardless of how many hours you sleep or when you nap. So splitting the light exposure into segments means potentially reducing melatonin by a lot. So far, no one has bifurcated the melatonin rhythm in human beings (despite a lot of really smart people trying).

Most of the great thinkers referenced in an earlier post would not have had access to electric light and LED backlit screens, they were awake at night but they were still living under a solar rhythm, doing their work late at night in circadian darkness.

The idea behind f.lux is to provide healthy darkness at night even when exposed to artificial light and that happens on a ~24 hour schedule. f.lux is designed to meet different needs and schedules, and as the science becomes more clear, f.lux will be updated accordingly. Even if what you are looking for is different from the way the f.lux software is designed to function, we still appreciate hearing about your needs and thoughts.