Build 37.7 for El Capitan

  • @herf So when's an official fix coming please? It's driving me nuts too ... I suspect Chrome may also be a factor here. MBP Mid 2012 Retina 15".

  • @herf Thanks. It seems that the bug is solved in 37.3.

  • do we?? really dont know

  • Since I upgraded to Build 37.2 with El Capitan, I have been getting orange screen often during the daytime. Also as noted in another post, this does not necessarily go away if I quit f.lux. This is just using safari or email. Can anyone help?

  • @pyris I have the same issue.

    Guys, please fix this. Since I upgraded to 37.2, I constantly get the "orange screen" i.e. "Bedtime" during the day. Mostly before noon. I then quit f.lux and the screen gets reset to "daytime" mode, but after a while it switches itself to "Bedtime" again even though the f.lux app isn't started. When I start f.lux, then screen fixes itself again. I'm doing this on and on and it drives me nuts.

    I went to System Preferences and disabled "Automatically adjust brightness", but that didn't help.

    I'm using El Captian 10.11.6 Beta (15G26a). I was also using an El Capitan Beta with f.lux v36, but I had no problems then.

  • @herf It appears with this new build that f.lux is deleting its color profile when it is daytime. Is this intended behavior or a bug?

  • @agottschling yes 37.3 does this - it helps fix unplugged monitors. Previously (37.2) f.lux would select the "old" profile and leave the last "f.lux profile" there. It doesn't seem that 37.3 has helped much.

    What's happening with the new 10.11.5 OS is that the system is remembering our profile even when we tell it to use the default one - in fact, unless we constantly tell it again and again to stop doing it (which is very expensive).

    Regarding the v37 update: the previous build (v36.6) in some cases was constantly setting your profile because the OS told us it was always changing, which is about 100x as expensive as not doing so. Apple seems to have fixed most of these bugs so far, so we released 37 after a few weeks of testing, and it's less aggressive about fixing this case.

    The remaining bugs seem to be related to Radeon chipsets and sometimes to automatic brightness. I'm trying to sort out which is which.

    It's complicated because we don't have a machine in-house that's exhibiting the bug.

  • @herf Ah. I understand now. I've got a MacBook Pro with the dual gpus (Radeon 6750m and Intel HD 3000). If I can be of any help testing, let me know.

  • @Katya-K. Can you post your machine type (and GPU type) also? thanks!

  • @herf

    Sure, here's my iMac info.

    alt text

  • Ok - the case that reliably fails for me on our Intel/NVIDIA machines is this one:

    1. Enable automatic brightness
    2. Disable it.
    3. Don't reboot!
    4. ...

    So if you are in this state, please reboot and don't change the automatic brightness setting after. AMD may be still another case.

  • Just wanted to say it seems the issue no longer occurs on my side. Here is what I remember I did:

    1. Installed f.lux 37.2
    2. Preferences -> Displays -> Color. I removed the f.lux display profile.
    3. "Automatically adjust brightness" stays enabled.
    4. Rebooted my iMac

    I thought f.lux is not going to work after I removed the profile, however, it does seem to work. I'm using the Classic f.lux theme. I'll update my info should any changes occur.

  • OK. I've found a replicatable scenario that will cause f.lux to get stuck, and whenever I leave Google Chrome open but minimized, it can "remember" the f.lux color profile such that when I maximize it, it will revert the display back to the old color. I'm running the latest stable build of chrome and flux 37.3.

  • Hi everyone,
    I have the following issue:
    When using f.lux in the evening and shutting down my computer, the next morning when I reboot my Computer the warm color temperature is active and my screen is, like in the evening orange. Only after a few seconds I got a flicker and the right temperature (6500K) is set.
    Can anybody help me?
    Thanks in advance. :)
    By the way ... I am running Mac OS X 10.11.6 (Macbook Pro Retina, 15', Mid 2014)/ 2.5 Ghz Intel Core i7 / 16 GB 1600 Mhz DDR3 / NVIDIA GeForce GT 750M 2048 M

  • I think this is expected to work this way (f.lux doesn't get time to run immediately on wake or reboot, so it takes us a minute to fix things from the previous night).

    Do you sleep the machine or shutdown? Sleeping might fix things a little faster.

  • @agottschling please send your system info and if you're using automatic brightness or not?

  • @herf Specs

    I do have automatic brightness turned on.

  • I'm also having this exact issue, except I am on 10.11.5. I ended up reverting to 36.6, and will keep using that version until this can be sorted out.

  • Can you please tell me how to disable or remove this terrible version of f.lux? I love the software but versions 37.2 and 37.3 are driving me INSANE, switching to sunset all through the day, whether I enable or disable the app. And now, having completely quit f.lux, and DELETED both the f.lux profile and then the Color LCD profile, it keeps switching my display to sunset mode. Despite not being enabled and there being no f.lux profile present for the monitor. What is going on??
    Mid 2012 Retina MBP, OS X 10.11.6, running on Intel integrated graphics.

  • Can someone please set your daytime color temperature to 6400K and see if this helps?

  • @herf I've done that now - will let you know if it misbehaves. Time is 9:55am AEST here (and time zone is set based on location).

  • @MatthewK thanks - I have two workarounds in mind, and one is basically a less noticeable version of this - but I'm hoping this works.

  • No issues so far - it was switching every minute or so previously, so this is definitely better so far. Please let me know if I can provide any more feedback. Thanks for your responsive help! I teach neuroscience and the regulation of sleep and I always recommend this to my students.

  • @MatthewK great - keep us posted!

    I posted this workaround at the top of the thread, and hopefully it will give some people a solution until we find a new trick to convince the OS to do what we ask. :)

  • All has been well across the day, and it's now shifting for sunset as it should. Thanks again.
    Sorry I missed the tip at the top of the page, but for some reason that post doesn't always display when I visit this thread.

  • Macbook pro 2009

    f.lux starts automatically during day and 6400k setting does not help

  • Okay I have posted a beta: 37.5, which will now try to flush settings into the system periodically. This shouldn't be noticeable, and it should be a lot more efficient than 36.6 was.

    EDIT: Updated to 37.5

    Hope this fixes everyone. Let me know.

  • I have made this the main download on the site.

  • @herf do we need to update to the latest version when we are using older versions of OS X (Yosemite and mountain lion)?? If not, I shouldn't be getting continual notices to update.

  • There are some small fixes in this build, but overall it shouldn't make a big difference. Sorry for the bugging. :)

    Our updater isn't sophisticated enough to say "If you're on Yosemite and have a really old version, offer an upgrade, but if it's a minor change, don't say anything" but that would be nice, huh?

  • @herf thanks . So I don't need to update, but if I do there are some small fixes that would work/help EVEN on older OS X versions as well?

  • Hello, I updated to 37.5 today. Did anything get added that checks the color profile every once in a while? I'm having an issue with my video card drivers where every time the color profile is changed my cursor jumps a little. It's not so much of a problem with flux since I can just enable fast transitions. But if I don't my cursor will be jumping around the screen like crazy during a transition. But I noticed that after this update my mouse jumps a little every 10 minutes or so. Is this correct or could it be caused by another application?

  • @Jespertheend Yes that would be the new build. Which GPU and Mac are you using?

    Previously: El Capitan's automatic brightness has been restoring old f.lux profiles and not letting us know, so we made this build to try to actually make the screen come back to daytime mode. We can do a little bit less though.

  • @herf I'm using a nvidia gtx 980 ti on a hackintosh. So it's a bit of a special case. But I remember having the same issue on my old iMac as well. An option to disable the checks would be nice, but I understand that you don't want to clutter the UI. Is it possible to check if the system has the wrong color profile and only change it when it actually does have the wrong profile?

  • @Jespertheend actually this is what we have always done. The bug that has been breaking us on El Capitan is when the OS reports that nothing has changed, but it actually has. Will make an option to do a little less.

  • @herf ah I see, thank you that would be nice. It's not impossible to work with but every once in a while your cursor just ends up where you didn't intend to put it.

  • @Jespertheend Ok I pushed a build that makes the behavior slower and adds a pref to disable it.

    And then if you want to disable the time-based behavior:

    defaults write org.herf.Flux flushSeconds 0

  • @herf ah, I hadn't thought about that. This way the UI is still clean, nice!
    Thank you very much :)

  • @herf hmm it seems like I'm still having the issue. But I believe it only happens after 5pm or so.

  • F.lux 37.5 and 37.6 ignore the "Disable for" any of my apps; though it sometimes works on the initial start of the app, but as soon as I switch to another app and back it stops working. Even the "Disable for an hour" doesn't work anymore. In both cases a notification is displayed, saying that it's deactivated, unfortunately it's not. Reinstalling F.lux, restarting of Mac didn't help. Furthermore, the change between active and disabled state of these versions is abrupt. Previous versions had a smooth transition in both directions, activating and inactivating F.lux, now its instantaneous.

    System information:
    iMac 20" Mid 2007, Mac OS "El Capitan" 10.11.6, ATI Radeon HD 2400 XT 128 MB

  • Hey everyone - we posted this build which fixes the disable bug - let us know if it helps?


  • @herf Seems to be working fine. Thanks a lot.

  • @herf just found this forum after having all sorts of issues in 37.2 / osx 10.11.6. (flux enabled after quitting app; turning night mode on and off randomly, etc.)

    Only been using the 37.7 patch for about 10 minutes but night mode has turned on then back off once already.

    Love the app even with the current problems, just wanted to provide more feedback.

  • @herf Hey, I'm running 37.7 on macOS Sierra with auto brightness adjustment still enabled, and I'm still seeing the weird behavior where when brightness adjustment is triggered, the flux color profile kicks in even when it's daytime..

  • @malorkus which machine is it?

  • @herf 13" retina Macbook Pro (early 2013).

  • Hey I have a Macbook pro 13 inch (16 gb ram, i7) and there is an issue with the lighter colors namely when watching youtube videos.
    If I move the mouse to make the screen react, the colors will go back to the right tones, however when the time marking and stuff goes away the color goes stupid, for clear tones.
    My software is up to date
    All of that bluea is poorly rendered white.

  • I'm having this issue still. El Capitan, 37.7, automatic brightness enabled. It keeps flipping back to a late evening one all morning, even after I quit flux.

    It didn't seem to have made a flux color profile, just standard LCD. 2016-10-09 09.56.20.png?dl=0 for my system details.

    I think another contributing factor is I always have the monitor not on full brightness, normally just a couple up from the bottom. 4 blocks up from the bottom.

  • 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 ( 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 (
    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!

Log in to reply