It seems DT no longer provides nightly for x86 osx!
why no prior notice. My last one had issue with preferance window being blank. I was hoping a new nightly will solve that.
You probably want to get it from here: current OSX Build - #863 by MStraeten
1 Like
Yes. I did that also. This build has a same issue. The blank preference window.
The only hack I came up with is to setup the preference now only in DT52 and then copy its darktablerc to nightly or Agx versions.
A new version will come to that thread soon enough.
1 Like
the nightly build is based on homebrew and they dropped support for macos13 which is used to build the intel package with github runners. (see drop support for macOS 13 by zisoft · Pull Request #19341 · darktable-org/darktable · GitHub)
My issue is not osx 13, I am running osx 15.6. It is the no support for x86 built.
If future DT begin to require M1 only and not running on my osx 15.6 or 16 than I guess I will run it on VB linux.
BTW I have same issue with both last nightly as well as your Agx builds. For some unknown reason preference window is blank in both of the builds!
it’s the issue of the machine doing the builds - the github runner for nightly x86 builds is on macos13 - so the build fails due to issues with dependencies no longer maintained and fixed for macos13.
You might build yourself, then you’re safe as long as all dependencies are maintained for intel based macOS on homebrew or macports …
BTW: i can’t reproduce that behaviour on my m1 macbook.
is that behaviour reproducible if you run darktable with a clean configuration (e.g. /Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test )
Did you file an issue for that on darktable github? without filing an issue there’s no hope for a fix 
Furthermore, those macos-13 GHA runners will be deprecated and gone soon, apparently leaving no Intel option for free tier at all.
1 Like
I ran the command as you suggested with with a new --configdir ~/.config/darktable_test". same issue blank preference window.
and yes I did file the issue.
I am glad and surprised that nightly for OSX_x86 is back.
I personally want to thank the developers for it. 
1 Like