![]() ![]() Both images are just not signed, that's all. There is clearly something wrong with the ARM image. ![]() Fixing issues with macOS security settings Depending on the version of macOS, there maybe some warnings causing darktable not to run. WIth the intel image I can easily right click and open it to bypass the quantine. latest release snapshots from the stable release branch snapshots from the master branch Universal Package Formats flatpak macOS These bundles support macOS versions starting with 11.3 (Big Sur). Consequently, this macOS warning will not be eliminated and all raised issues that expect such a result will just be closed. I want to emphasize that the very existence of a macOS complaint about the alleged "damage" of darktable dmg is not a darktable bug, it is simply a consequence of the fact that the dmg is not digitally signed because it requires an expensive Apple developer account. If this does not solve the problem, then it is really worth raising a separate issue and research, because it would mean that there is an error in the recipe for solving the problem. I would like to clarify: are you saying that the actions suggested on the darktable dmg file download page (see screenshot below) do not fix the problem? The page has advice on what to do in this case. On the page I linked, one of the two possible system warnings mentioned is what you describe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |