Make sure DT has write permission for its cache in your home folder.
You might check, if your ~/.cache/darktable exists. macOS 15 changed security requirements, so you might grant darktable drive access.
current 4.9 build + a couple of RF lensfun data from: Kameratrollet
darktable-4.9.0+1164~g2702ef6efa_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+1164~g2702ef6efa_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md
difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub
3 Likes
current 4.9 build + a couple of RF lensfun data from: Kameratrollet
darktable-4.9.0+1181~gfa54963782_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+1181~gfa54963782_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md
difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub
2 Likes
current 4.9 build + a couple of RF lensfun data from: Kameratrollet
darktable-4.9.0+1257~ge8af3a5c1e_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+1257~ge8af3a5c1e_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md
difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub
just a few days until code freeze for 5.0 so don’t forget to report issues …
2 Likes
last 4.9 build before 5.0 freeze + a couple of RF lensfun data from: Kameratrollet
darktable-4.9.0+1284~g702f8aca84_arm64.dmg (macOS >= 11.3)
darktable-4.9.0+1284~g702f8aca84_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 4.9 release: https://github.com/darktable-org/darktable/blob/master/RELEASE_NOTES.md
difference to released 4.8.1 see: Comparing release-4.8.1…master · darktable-org/darktable · GitHub
2 Likes
After installation when I try to open the app I get a dialog saying the app is broken and the only action I get is move it to the trash.
4.8.1 working fine.
Apple M1 Pro 14.6.1 (Sonoma)
tried xattr -c but I got the error message: “Read-only file system”
Could you help me pinpoint the issue? Are there any logs anywhere I could provide you?
Is this information helpful?
it seems you’re running it from the mounted dmg - that’s write protected. So maybe copy the app into a location where you have write access before xattr -c
1 Like
Thank you it worked. It was my fault, I was trying to use xattr -c on the mounted image instead of the installed application.
For future reference: after installing darktable using the .dmg file I ran: xattr -c /Applications/darktable.app
After this I was able to open the application
current 5.0.x bugfix build + a couple of RF lensfun data from: Kameratrollet
darktable-5.0.0+17~g53ce7a831b_arm64.dmg (macOS >= 11.3)
darktable-5.0.0+17~g53ce7a831b_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 5.0.x release: darktable/RELEASE_NOTES.md at darktable-5.0.x · darktable-org/darktable · GitHub
difference to released 5.0 see: Comparing release-5.0.0...darktable-5.0.x · darktable-org/darktable · GitHub
2 Likes
current 5.0.x bugfix build + Canon R1 and R5mII support by Adding new camera support in darktable / LibRaw / ExifTool – Pandas Welt + a couple of RF lensfun data from: Kameratrollet
darktable-5.0.0+41~gfcb398ee9d_arm64.dmg (macOS >= 11.3)
darktable-5.0.0+41~g3819449f05_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 5.0.x release: darktable/RELEASE_NOTES.md at darktable-5.0.x · darktable-org/darktable · GitHub
difference to released 5.0 see: Comparing release-5.0.0…darktable-5.0.x · darktable-org/darktable · GitHub
2 Likes
current 5.0.x bugfix build + Canon R1 and R5mII support by Adding new camera support in darktable / LibRaw / ExifTool – Pandas Welt + a couple of RF lensfun data from: Kameratrollet
darktable-5.0.0+58~g08bf23744a_arm64.dmg (macOS >= 11.3)
darktable-5.0.0+58~g6e5562a8a8_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 5.0.x release: darktable/RELEASE_NOTES.md at darktable-5.0.x · darktable-org/darktable · GitHub
difference to released 5.0 see: Comparing release-5.0.0…darktable-5.0.x · darktable-org/darktable · GitHub
2 Likes
current 5.0.x bugfix build + Canon R1 and R5mII support by Adding new camera support in darktable / LibRaw / ExifTool – Pandas Welt + a couple of RF lensfun data from: Kameratrollet
darktable-5.0.0+79~g6b24dca65a_arm64.dmg (macOS >= 11.3)
darktable-5.0.0+79~ga89dc6cf5a_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 5.0.x release: darktable/RELEASE_NOTES.md at darktable-5.0.x · darktable-org/darktable · GitHub
difference to released 5.0 see: Comparing release-5.0.0…darktable-5.0.x · darktable-org/darktable · GitHub
2 Likes
current 5.0.x bugfix build + Canon R1 and R5mII support by Adding new camera support in darktable / LibRaw / ExifTool – Pandas Welt + a couple of RF lensfun data from: Kameratrollet
darktable-5.0.0+93~g0cd50e2205_arm64.dmg (macOS >= 11.3)
darktable-5.0.0+93~g1a0b35b398_x86_64.dmg (macOS >= 10.14)
you might run it with an in-memory library via terminal:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --library :memory:
or use a separate config directory:
/Volumes/darktable/darktable.app/Contents/MacOS/darktable --configdir ~/.config/darktable_test
also keep in mind that if you don’t disable writing sidecar files these can be messed up
both packages are unsigned, you might need to allow execution via terminal: " xattr -c <path/to/application.app> "
Release notes for 5.0.x release: darktable/RELEASE_NOTES.md at darktable-5.0.x · darktable-org/darktable · GitHub
difference to released 5.0 see: Comparing release-5.0.0…darktable-5.0.x · darktable-org/darktable · GitHub
3 Likes
Sorry if this has been covered, I have tried searching this thread (and elsewhere), but have not found answers to solve the issues/answer the questions.
M1 Mac Mini running Sequoia 15.2.
Until this morning I was running 5.0.0+58. For some reason some shortcuts were not working (they worked on previous versions). Basic tasks like select all (cmd+a) in Lighttable view pop up a small window that states “not active.” This function appears to be active in the settings/shortcuts, and also appears to be set up in config. It also works on the mac in other programs. I have tried restoring defaults, restarting etc - but no luck. Just updated to 5.0.0+93, and the same issue. Is there something obvious that I’m missing?
Also, I always see the warning: “also keep in mind that if you don’t disable writing sidecar files these can be messed up.” I’ve had this enabled in the past, without any issues that I was aware of (maybe just lucky?). But i have turned it off now. Is there a specific reason why it’s best to not write sidecar files? Better to just have the data saved in the database? Just curious how it gets messed up.
Thanks in advance for any guidance, and really appreciate all the hard work that goes into making this available for us on the Macs.
Scott
If you don’t have defined custom shortcuts you might rename ~/.config/darktable/shortcutsrc to a different name to let darktable recreate the default shortcuts.
Since currently these builds are based on the bugfix branch there are just bugfixes and no new functions that might break compatibility. So the risk of messing up xmps is negligible. That will change after bugfix release is out and these builds will head onto next release …
Thanks so much for the reply! I’ll give a shot at having DT recreate the the defaults, since I do not have any custom shortcuts at the moment.
So it looks like I can use XMP for now - and just be careful when there is a major update? I only have the xmp created after I have made some edits - which always felt safe. But [knock on wood] it’s not like I have ever had to recall edits using the XMPs. So either way, I suppose I’m fine using whichever method is safest for the program’s overall stability.
Appreciate your help!
UPDATE: Just did as you suggested, and for some reason “select all” is still not working. I did confirm that it is again listed in the settings section as assigned. I also confirmed that other basic functions utilizing the command key work. undo and duplicate work as they should.
I checked the build and wasn’t able to reproduce. Maybe file an issue at GitHub · Where software is built