f.lux

    f.lux forum
    • Register
    • Login
    • Search
    • Recent
    • Popular

    F.lux not supported in macOS high sierra

    macOS
    20
    41
    29139
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mfield last edited by

      There does seem to be something wrong with display profiles and colorsync on High Sierra 10.3.2. I'm unable to switch profiles manually, and flux doesn't seem to be able to either.

      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.

      1 Reply Last reply Reply Quote 0
      • herf
        herf last edited by

        If you are having this problem please note if you are using a DCI P3 model mac (newer iMacs and Macbook pros I think) or an older model.

        We have not tested enough on these yet...

        Sjoerd Bergmans 1 Reply Last reply Reply Quote 0
        • Sjoerd Bergmans
          Sjoerd Bergmans @herf last edited by Sjoerd Bergmans

          @herf

          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..

          1 Reply Last reply Reply Quote 0
          • M
            mfield last edited by

            @herf
            I am indeed running a brand new 2017 iMac.

            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.

            0_1516915836215_Screen Shot 2018-01-25 at 4.30.21 PM.jpg

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

            herf ? Sjoerd Bergmans 3 Replies Last reply Reply Quote 0
            • herf
              herf @mfield last edited by herf

              I don't recommend deleting profiles in the system, only choosing a different one.

              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.

              1 Reply Last reply Reply Quote 0
              • M
                mfield last edited by

                @herf

                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.

                herf 1 Reply Last reply Reply Quote 0
                • herf
                  herf @mfield last edited by

                  @mfield very interesting...thanks.

                  1 Reply Last reply Reply Quote 0
                  • ?
                    A Former User @mfield last edited by

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • M
                      mfield last edited by

                      @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.

                      1 Reply Last reply Reply Quote 0
                      • Sjoerd Bergmans
                        Sjoerd Bergmans @mfield last edited by

                        @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..

                        1 Reply Last reply Reply Quote 0
                        • herf
                          herf last edited by

                          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).

                          1 Reply Last reply Reply Quote 0
                          • Eugenio Padilla
                            Eugenio Padilla last edited by Eugenio Padilla

                            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.

                            1 Reply Last reply Reply Quote 0
                            • ?
                              A Former User last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • M
                                mfield last edited by

                                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 :)

                                1 Reply Last reply Reply Quote 0
                                • Eugenio Padilla
                                  Eugenio Padilla last edited by

                                  I am on 10.13.3 and the issue persists just like in previous versions.

                                  1 Reply Last reply Reply Quote 0
                                  • Fran Walpe
                                    Fran Walpe last edited by

                                    I'm on 10.13.3 and observed this issue, but fixed after a reboot.

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      sierrafluxnoluv last edited by sierrafluxnoluv

                                      How is this performing on 10.13.4?

                                      1 Reply Last reply Reply Quote 0
                                      • Eugenio Padilla
                                        Eugenio Padilla last edited by

                                        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.

                                        Sjoerd Bergmans 1 Reply Last reply Reply Quote 0
                                        • Sjoerd Bergmans
                                          Sjoerd Bergmans @Eugenio Padilla last edited by

                                          @Eugenio-Padilla

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

                                          1 Reply Last reply Reply Quote 0
                                          • N
                                            New2This @bobzippymail last edited by

                                            @bobzippymail
                                            I'm somewhat of a neophyte, Bob. How do I do this? Step by step 😜

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright © 2014 NodeBB Forums | Contributors