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

    Failed upgrade from 36.4 to 36.5

    macOS
    4
    13
    9.5k
    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.
    • T
      timblair
      last edited by

      Hey there,

      I'm currently running 36.4, and got a notification about upgrading to 36.5. However, attempting to perform that upgrade resulted in an "Update Error!" dialog box appearing.

      "Update Error!" dialog box

      Is there any way I can find out more about why the upgrade failed?

      Possibly relevant: I installed f.lux using Homebrew Cask.

      Thanks!

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

        Thanks for the note about Cask - generally this means that the Sparkle updater could not write the downloaded zip file.

        My suspicion is we're seeing this error when one user downloaded and another is trying to update (and Cask might be running as admin/root?)

        The usual location is here, so please check if this area is writable?
        ~/Library/Application Support/Flux/.Sparkle/

        T 1 Reply Last reply Reply Quote 0
        • J
          jjmaxwell
          last edited by

          I am getting the same error everyday. I've tried updating 4 times now (whenever I'm prompted after rebooting my computer it seems). Each time "Upgrade Failed"

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

            Hey @herf. ~/Library/Application Support/Flux is writeable; ~/Library/Application Support/Flux/.Sparkle doesn't exist (although it could be created), and the update process is running through the f.lux app (i.e. I'm not running manual update via Cask, and it's not being run automatically either). The original install (via Cask) was done as my user, not root.

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

              Is your machine a Macbook Pro?

              I'm wondering if f.lux is taking too long to exit and this is messing up the updater.

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

                @herf Yes, MacBook Pro (Retina, 15-inch, Late 2013), running El Capitan (10.11.1).

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

                  Also, did the update prompt happen at night?

                  I think f.lux on a MBP will take longer to exit at night, because it has to reset the system profile.

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

                    @herf I had one failure at night, but one also during the day.

                    1 Reply Last reply Reply Quote 0
                    • lornaL
                      lorna
                      last edited by

                      UPDATE: Amazon is not serving secure enough files for OSX 10.11.1 to install, so it's failing. We're rehoming the download now.

                      @lorna

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

                        Should be working now.

                        1 Reply Last reply Reply Quote 0
                        • lornaL
                          lorna
                          last edited by

                          And thank you for all your assistance with this, it helped us find the problem much faster. Sorry about the error!

                          @lorna

                          1 Reply Last reply Reply Quote 0
                          • T
                            timblair
                            last edited by

                            Great news. Is there any way I can force an update, or do I just have to wait for the auto-updater to kick in in its own time?

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

                              You can do this at Terminal and relaunch after:

                              defaults delete org.herf.Flux SULastCheckTime

                              We have a button in the next version. :)

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