My laptop is

• Macbook Pro 15" Late 2011

Hope this helps you or anyone else.

Thanks f.lux, keep it up!

The drivers are really screwed up on 10.13.6, and it needs a fix from Apple, but we've posted a workaround for now.

Seemed to happen after I deleted the cache in order to solve another problem with the calendar agent using 100% of the cpu and running hot. Recently upgraded from El Capitan to High Sierra. Running 10.13.5 too.

I take it no one has found a solution if the most recent High Sierra updates didn't solve the problem?

Makes me jealous. It still doesn't work for me. No response whatsoever.. not from flux, nor from the built-in Night-Shift

I've moved all my various profiles back into place, and it's all behaving the way it should.

Definitely good news :)

The issue seems to happen to me when the Intel Iris Pro GPU is used. When I launch Photos.app, the computer switches to the AMD GPU (Radeon R9 M370X 2 GB), and I suddenly get the f.lux tint. I then quit Photos.app, and I go back to see un-tinted content.

I use iStat Menus, and the CPU component also shows the currently used GPU. Launching Photos.app does switch to the AMD GPU, and quitting it goes back to Intel. Additionally, if I disconnect the laptop charger while Photo.app is running, I again go back to no f.lux tinting, and iStat Menus shows that the computer went back to Intel Iris Pro.

It seems this bug happens only while using the Intel Iris Pro GPU.

I am guessing the system is somehow failing to load the sRGB profile and then not letting anyone change the setting. Wonder if a Mac in this state would load a fake sRGB profile from ~/Library/Colorsync/ (but probably not).

I also haven't got the "~/Library/Colorsync/" directory, instead I have "~/Library/ColorPickers" which holds a number of .icc files..

The problem was an inability to choose a different profile. It was full on stuck on the sRGB profile.
I could not manually switch, and both f.lux and night shift were having the same issue.

I do agree that this isn't even close to ideal. It would be better to figure out what was causing it to stick.

The sRGB profile is usually used as a reference (target), not for a display profile, and the "iMac" or "Color LCD" one is preferred.

We will try to borrow a newer Mac and see what we find out about the wider-gamut screens and how they are reading profiles.

I found a fix, though!

I noticed that my monitors were stuck on an sRBG profile I had never switched to in the first place.
Assuming there was something wrong with that profile (and maybe others,) related to a change in 10.3.2, I went ahead and deleted it. And every other unused profile I could find.
I did keep my iMac's default profile.

These were found in:
~/Library/Colorsync/Profiles/
/Library/Colorsync/Profiles/
/System/Library/Colorsync/Profiles/
/Library/Application support/Adobe/Color/Profiles/

I can't tell you which was actually causing the problem, and it may be better to go through them one at a time until you find THE profile responsible.

I'm now able to manually swtich profiles, as well as let F.Lux do its' thing.

I should note that Colorsync utility's profile verify/repair couldn't find anything wrong.

I am running macOS 10.13.2 on a MacBookAir6,2 with a 1,3 GHz Intel Core i5.

I explained my problem in one of the earlier post: neither Flux nor the build in Night Shift is working..

I took a look at the console. There are many messages regarding Flux whenever I launch it. Unsure of which messages to post I picked 2 that stood out for me.

One was: "ColorSync: ColorSyncProfileCreateWithDisplayID failed to get profile for kColorSyncDisplayDeviceClass" which was from the com.apple.colorsync subsystem. - I saw the same error was mentioned here by @mfield earlier.

The other one that stood out was "Function boringssl_session_errorlog: line 2829 [boringssl_session_read] SSL_ERROR_ZERO_RETURN(6): operation failed because the connection was cleanly shut down with a close_notify alert" of the com.apple.network.boringssl subsystem. This one stood out because there were about 10 exact copies of it in the console.

Hope any of this helps, would be glad to help to further diagnose the problem but will need some guidance.

I am however fairly familiar with the command-line and basic programming so not a total noob.

Hope there's a solution soon as each evening I get more frustrated at not being able to properly dim / color the screen.

EDIT: I just tried launching Flux with sudo and I got the following output:

2018-01-25 20:59:13.279 Flux[15999:1232188] Got response 200
2018-01-25 20:59:13.280 Flux[15999:1232188] Skipping offer 1 because it has expired

Flux stil does not work..

We have not tested enough on these yet...

From Console:
Flux (Colorsync)
Subsystem: com.apple.colorsync Category: org.herf.Flux
ColorSync: ColorSyncProfileCreateWithDisplayID failed to get profile for kColorSyncDisplayDeviceClass

When I try to create a new profile with Apple's Display Calibrator Assistant:
An error occurred.
The new calibrated display profile could not be created or set to be the current profile for this display.

I've checked read/write permissions in all the appropriate places, tried the backgrounditems trick, removed various colorsync and display preferences related plists, reset pram and all.

I think it may be up to Apple to fix this one.