F.lux not supported in macOS high sierra
-
This post is deleted! -
@KneelMan
Deleting anything in /System isn't possible without first turning off System Integrity Protection. You can google how to disable it, but know that it opens up your computer to a number of risks.
If anything, do what you need to with the profiles, then re-enable it. -
@mfield Strange, I just noticed when I check out my screen color profiles via System Settings, I haven't even got a f.lux profile though I've been using F.lux for years, is this strange?
I also haven't got the "~/Library/Colorsync/" directory, instead I have "~/Library/ColorPickers" which holds a number of .icc files..
-
f.lux profile is only for dual-GPU macs. We do it only when we have to in order to keep the screen from flashing - the normal one is restored during the day.
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 have this issue on a Mid-2015 15" MacBook Pro (11,5). It still happens on macOS 10.13.3.
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.
-
This post is deleted! -
10.13.3 does seem to fix things on Apple's end!
I've moved all my various profiles back into place, and it's all behaving the way it should.
Definitely good news :)
-
I am on 10.13.3 and the issue persists just like in previous versions.
-
I'm on 10.13.3 and observed this issue, but fixed after a reboot.
-
How is this performing on 10.13.4?
-
macOS 10.13.4 seems to have finally fixed this for me! It's the first time it consistently works since upgrading to High Sierra.
-
Makes me jealous. It still doesn't work for me. No response whatsoever.. not from flux, nor from the built-in Night-Shift
-
@bobzippymail
I'm somewhat of a neophyte, Bob. How do I do this? Step by step 😜 -
Have this same problem. Have a blue tint, F.lux isn't working, and can't change the display colour profile at all. It's locked on the sRGB profile. And disabling System Protection Integrity and deleting the file didn't work either.
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?
-
On my brand new machine 2018 Macbook Pro 15" - running the latest OS - the latest version of flux is still showing the error. @herf , is there a fix close to complete?
-
There is a thread about the newest Macbook Pro over here:
https://forum.justgetflux.com/topic/6579/blacks-turn-cyan-on-newest-macbook-pro/1The drivers are really screwed up on 10.13.6, and it needs a fix from Apple, but we've posted a workaround for now.
-
I am using macOS High Sierra 10.13.6 and it works just fine.
My laptop is
- Macbook Pro 15" Late 2011
Hope this helps you or anyone else.
Thanks f.lux, keep it up!
