F.lux isn't working anymore (so does Night Shift)
It's been several weeks now since I'm attempting to solve this problem, only I haven't found any solution. F.lux does not «work» anymore, as in the application promptly launches but, in terms of brightness and dimming, nothing happens. It's the same for Apple's built-in Night Shift although I never use it. I tried everything from system updates, full check and repair of my SSD drive and various color profiles, complete uninstall and reinstall of the F.lux app, SMC and PRAM resets — nothing has worked so far.
Is anyone else currently experiencing this problem? I've read that some people had solved similar issues with a simple reboot, but my case seems more complicated. My computer is a 15 "MacBook Pro (Late 2013). My macOS version is 10.13.4 (17E202). The only thing I noticed during my many attempts to solve this is that F.lux color profile seems to be damaged (see screenshot attached). This doesn't explain why Night Shift doesn't work either. If anyone can help me, my poor eyes can't take it anymore!
Thanks in advance,
Dreamburger last edited by
Anyone has been experiencing this lately? Any solution?
Transgredi last edited by
I have exactly the same issue. Both Night Shift and f.lux do not work any more and apparently the root cause are broken colour profiles. I tried everything - rebooting, clearing all caches, reseting PRAM and SMC. Nada... Nothing worked... :/
Perhaps it's fixed in 10.13.5? Just released yesterday and haven't installed it yet.
@transgredi Unfortunately the latest macOS update didn't solve anything… on my computer at least.
It would be greatly appreciated if anyone who has experienced this, or even someone from the F.lux team, could help us solve this matter. I don't believe two random people can be experiencing the exact same problem at the same time. There must be others stuck in the same situation. From what I've read, it's not the first time this happens.
There is a "locked profile" issue reported in this thread, but we have not seen it here:
My impression of this bug is as follows: the machine is using a non-display profile (e.g., "sRGB profile") during upgrade, and 10.13 then seems to fail to load it, but also disallows removing or changing it, so the color system gets stuck with no profile.
@herf Indeed, my computer is locked on that sRGB IEC61966-2.1 profile and unfortunately it isn't possible to change it (as mentioned in that other thread).
I'm surprised some people managed to fix this, while I don't, even after trying what's been brought up in terms of solution as well as numerous new updates from Apple.
Transgredi last edited by Transgredi
Same here - I tried all advices on how to fix the issue and none of them worked :/ I'm stuck on that generic profile sRGB IEC61966-2.1.