I have been using Darktable for a few years on my iMac. It works fine, albeit slowly, so I was excited to see how fast it would go on my new MacBook Air M3. So I installed 4.6.1 for Arm, launched it and nothing happens. I just get a blank screen with three menu items: darktable, view and help. And it keeps other apps from launching, so I have to force quit it. Any ideas?
Did you follow the instructions on the install page?
Tried that. No change.
Can you be more specific about what you did please?
Since Darktble was already installed, I used this command: xattr -dr com.apple.quarantine /Applications/darktable.app in Terminal, but it didn’t change anything. Is there a Terminal command to remove Darktable completely, including all the hidden files, so that I can start from a clean slate? Or maybe install it with Homebrew?
You can delete the .app and then try the terminal commands before you install it. Other files are in ~/.config/darktable.
So, here is what I did:
- Deleted the app with AppCleaner
- Deleted the Darktable folder from .config, .local and .share just to be safe;
- Downloaded a new version of 4.6.1
- Ran the Terminal command on that .dmg
- Moved the Darktable app to the Applications folder, as normal;
- Launched Darktable.
- Still get only a blank screen. No messages, nothing. Plus, it crashes the Finder as well.
I don’t know what else I can try…
You can start it from the the terminal, something like /Applications/darktable.app/bin/darktable -d all. I am not sure of the path since I’m not a Mac user. If you can launch it that way, please paste any terminal output here.
Also ping @MStraeten since he’s doing a lot of nice Mac builds.
at least with 3 different M3 and a M3max machine in the local apple store my arm64 build from current OSX Build - #754 by MStraeten runned fine:
- download it
- run from terminal:
xattr -c ~/Downloads/darktable-4.7.0+1237~gfdedc3dae2_arm64.dmg - double click the dmg
- run from terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_dummy
if there’re issues then attach the output as a text file
Hi. Thanks for your help.
Here is what I got after running the Terminal command:
(process:1170): GLib-GObject-CRITICAL **: 12:37:22.031: g_object_set: assertion ‘G_IS_OBJECT (object)’ failed
(darktable:1170): Gtk-CRITICAL **: 12:37:22.296: gtk_window_add_accel_group: assertion ‘GTK_IS_WINDOW (window)’ failed
2024-05-18 12:37:24.927 darktable[1170:17633] WARNING: Secure coding is automatically enabled for restorable state! However, not on all supported macOS versions of this application. Opt-in to secure coding explicitly by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState:.
that’s all?
Please try /Volumes/darktable/darktable.app/Contents/MacOS/darktable -d common --configdir ~/.config/darktable_dummy
Well, that got more of a result!
darktable 4.7.0+1237~gfdedc3dae2-dirty
Copyright (C) 2012-2024 Johannes Hanika and other contributors.
Compile options:
Bit depth → 64 bit
Debug → DISABLED
SSE2 optimizations → DISABLED
OpenMP → ENABLED
OpenCL → ENABLED
Lua → ENABLED - API version 9.3.0
Colord → DISABLED
gPhoto2 → ENABLED
GMIC → ENABLED - Compressed LUTs are supported
GraphicsMagick → ENABLED
ImageMagick → DISABLED
libavif → ENABLED
libheif → ENABLED
libjxl → ENABLED
OpenJPEG → ENABLED
OpenEXR → ENABLED
WebP → ENABLED
See resources | darktable for detailed documentation.
See Sign in to GitHub · GitHub to report bugs.
0.0042 application_directory: /Volumes/darktable/darktable.app/Contents/MacOS
0.0043 darktable.datadir: /Volumes/darktable/darktable.app/Contents/Resources/share/darktable
0.0043 darktable.plugindir: /Volumes/darktable/darktable.app/Contents/Resources/lib/darktable
0.0043 darktable.localedir: /Volumes/darktable/darktable.app/Contents/Resources/share/locale
0.0044 darktable.configdir: /Users/sergelheureux/.config/darktable_dummy
0.0047 darktable.cachedir: /Users/sergelheureux/.cache/darktable
0.0047 darktable.sharedir: /Volumes/darktable/darktable.app/Contents/Resources/share
0.0047 darktable.tmpdir: /private/var/folders/73/m_1_7k7s4rl3md_ggnf4y9gh0000gn/T
0.0047 new_xdg_data_dirs: (null)
(process:927): GLib-GObject-CRITICAL **: 14:53:05.055: g_object_set: assertion ‘G_IS_OBJECT (object)’ failed
0,1501 [dt_worker_threads] using 6 worker threads
0,1502 [dt_configure_runtime_performance] found a sufficient 64-bit system with 8192 Mb ram and 8 cores
0,1502 [dt_get_sysresource_level] switched to 1 as `default’
0,1502 total mem: 8192MB
0,1502 mipmap cache: 1024MB
0,1502 available mem: 4096MB
0,1502 singlebuff: 64MB
0.1554 [opencl_init] opencl disabled via darktable preferences
0.1559 [opencl_init] opencl library ‘/System/Library/Frameworks/OpenCL.framework/Versions/Current/OpenCL’ found on your system and loaded, preference ‘default path’
0.1563 [opencl_init] found 1 platform
[opencl_init] found 1 device
[dt_opencl_device_init]
DEVICE: 0: ‘Apple M3’
CONF KEY: cldevice_v5_appleapplem3
PLATFORM, VENDOR & ID: Apple, Apple, ID=16940800
CANONICAL NAME: appleapplem3
DRIVER VERSION: 1.2 1.0
DEVICE VERSION: OpenCL 1.2
DEVICE_TYPE: GPU, unified mem
GLOBAL MEM SIZE: 5461 MB
MAX MEM ALLOC: 1024 MB
MAX IMAGE SIZE: 16384 x 16384
MAX WORK GROUP SIZE: 256
MAX WORK ITEM DIMENSIONS: 3
MAX WORK ITEM SIZES: [ 256 256 256 ]
ASYNC PIXELPIPE: NO
PINNED MEMORY TRANSFER: NO
AVOID ATOMICS: NO
MICRO NAP: 250
ROUNDUP WIDTH & HEIGHT 16x16
CHECK EVENT HANDLES: 128
TILING ADVANTAGE: 0.000
DEFAULT DEVICE: NO
KERNEL BUILD DIRECTORY: /Volumes/darktable/darktable.app/Contents/Resources/share/darktable/kernels
KERNEL DIRECTORY: /Users/sergelheureux/.cache/darktable/cached_v3_kernels_for_AppleAppleM3_1210
CL COMPILER OPTION: -cl-fast-relaxed-math
CL COMPILER COMMAND: -w -cl-fast-relaxed-math -DAPPLE=1 -I/Volumes/darktable/darktable.app/Contents/Resources/share/darktable/kernels
KERNEL LOADING TIME: 0.0394 sec
[opencl_init] OpenCL successfully initialized. internal numbers and names of available devices:
[opencl_init] 0 ‘Apple Apple M3’
0.2096 [opencl_init] FINALLY: opencl PREFERENCE=OFF is AVAILABLE and NOT ENABLED.
0.2110 [opencl_init] set scheduling profile to default, setup has changed.
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 -1 0 0 -1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[opencl_synchronization_timeout] synchronization timeout set to 200
UNIFIED MEM SIZE: 2048 MB reserved for ‘appleapplem3’
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 -1 0 0 -1
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[opencl_synchronization_timeout] synchronization timeout set to 200
0,2574 [dt_worker_threads] using 6 worker threads
(darktable:927): Gtk-CRITICAL **: 14:53:05.317: gtk_window_add_accel_group: assertion ‘GTK_IS_WINDOW (window)’ failed
2024-05-18 14:53:08.126 darktable[927:9785] WARNING: Secure coding is automatically enabled for restorable state! However, not on all supported macOS versions of this application. Opt-in to secure coding explicitly by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState:.
@serge70 can you please test if this problem also exists with the nightly build?
Yes, it does. And it crashed the Finder as well.
Unfortunately that report doesn’t indicate issues.
Are there any hints in the macOS system log files?
Do you have Xcode or Xcode commandline installed? Then maybe running darktable within the debugger might give more insights.
Well, this is weird. I finally managed to launch Darktable, in a somewhat unexpected way: by disconnecting my USB-C hub. It runs fine now. I tried reconnecting the hub and, sure enough, Darktable crashed. I am glad that I finally found the problem, but it is somewhat inconvenient since my external monitor is plugged in to that hub. Thanks for your help, and for your OSX builds!