Mario Zimmermann

Linux gives a successful return code 0 with that unitialized mutex: https://github.com/zisoft/darktable/actions/runs/4352436229/jobs/7605222123#step:6:575 Windows as well, return code 0: https://github.com/zisoft/darktable/actions/runs/4352436229/jobs/7605220970#step:6:607 So it seems that only the macOS implementation handles that correctly.

Anyway, an `assert()` on a return value which may or may not be undefined does not give any benefit

That's correct and now we can hopefully stop blaming macOS for the failing CI 🙂

I just followed the instructions in [BUILD_hb.txt](https://github.com/darktable-org/darktable/blob/master/packaging/macosx/BUILD_hb.txt), steps 1 and 2 ran smoothly. The executable ./bin/darktable can be run from the command line and seems to work fine. When trying...

Yes, that works. Thank you! Are you going to make a PR for this fix? EDIT: Ah, sorry. I just saw you already did 👍

> After clicking Copy and Import, I get a full screen reminder prompt to adjust import settings. I cannot reproduce on an Intel Mac with Sonoma: German: After clicking on...

> MacOS 12.7.4 @MStraeten: These are clearly the MacPorts builds. Can you reproduce? @Sebby319: Because you are on macOS 14.x, can you try with `darktable-4.6.1-arm64.dmg` from the [release page](https://github.com/darktable-org/darktable/releases/tag/release-4.6.1) and...

> attempt to write a readonly database Check the file permissions of `library.db` and `data.db` in your config folder.

The slider handles look different (hollow triangles):

Maybe the same issue? https://discuss.pixls.us/t/darktable-4-6-mac-lighttable-scrolling-stops-responding/41176