SUMMARY Since updating to MacOS 15.1, I cannot start digikam anymore. The message I get is "The application dock does not have permission to open (null)". I assume this is due to missing code signing. Following this forum solved the issue for me: https://discussions.apple.com/thread/255827087?sortBy=rank STEPS TO REPRODUCE 1. Open digikam from Launchpad 2. See error message 3. OBSERVED RESULT App does not start EXPECTED RESULT App would start as before SOFTWARE/OS VERSIONS Windows: - macOS: 15.1 (Intel) (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: 5 ADDITIONAL INFORMATION
I hava the same problem on an Intel MacBook Pro 16 inch 2019 after upgrading to macOS 15.1. I previously downloaded and installed the legacy version https://files.kde.org/digikam/legacy/digiKam-8.5.0-20241027T124153-Qt5-MacOS-x86_64.pkg and the problem still exists. I just upgraded to macOS 15.1.1 and downloaded the current Mac Intel pre-release https://files.kde.org/digikam/legacy/digiKam-8.6.0-20241121T055349-Qt5-MacOS-x86_64.pkg and the problem still exists. As suggested in Bug 49562 (https://bugs.kde.org/show_bug.cgi?id=495628#c7) I read the apple community post and ran command "sudo codesign --force --deep --sign - ./digikam.app" from the ./Applications/digiKam.org folder. After the command completed, I was able to open digiKam from the finder without any problems. I hope this information assists with fixing this bug. Thank you again for your time and efforts.
Hi Alex and Mark, This isn't a bug in digiKam, but is caused by the way macOS validates packages. Since digiKam is an open-source project, we don't have the keys to sign the program the way Apple wants it. In a commercial package, Apple would issue keys to the company to sign the program with "official" keys. That's the codesign command you added below. By doing codesign yourself, you are authorizing the program to run on your computer. We appreciate the tip about codesign. We'll add that to the documentation. Cheers, Mike
Read the paper here : https://hackaday.com/2024/11/01/apple-forces-the-signing-of-applications-in-macos-sequoia-15-1/ It's a shame. I refuse to pay to Apple 99 euros by year. To support this OS, they must pay open source developers instead... I'm sure that Microsoft will follow the same way as the same mechanism exists under Windows. Best Gilles Caulier
This long story is very instructive : https://forums.macrumors.com/threads/bug-or-intentional-macos-15-1-completely-removes-ability-to-launch-unsigned-applications.2441792/ Sounds like to auto sign is not required all the time. plist file must be updated, but how... Gilles
It sound like a bug in MacOS 15.1 : https://forums.macrumors.com/threads/bug-or-intentional-macos-15-1-completely-removes-ability-to-launch-unsigned-applications.2441792/page-2?post=33554771#post-33554771 Gilles
There is a solution without to self sign a package : removing the quarantine flag : xattr -d com.apple.quarantine $FILE Its explained in this another paper : https://www.osnews.com/story/141055/bug-or-intentional-macos-15-1-completely-removes-ability-to-launch-unsigned-applications/ Gilles
*** Bug 496828 has been marked as a duplicate of this bug. ***
This article resume well the situation: https://iboysoft.com/tips/the-application-finder-does-not-have-permission-to-open-null.html Gilles Caulier
*** Bug 497285 has been marked as a duplicate of this bug. ***
Hi, digiKam 8.6.0 is just released: https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ Problem still exists with this version? Thanks in advance Gilles Caulier
Hello Gilles, unfortunately the problem still exists. I had to run the codesign command again before I could open digikam 8.6.0
Same here. It does not open.
(In reply to copperlanding from comment #12) > Same here. It does not open. Since I am not a Mac expert: Is there an easy to understand workaround? I have to stay with version 8.5.0 unfortunately. Thanks in advance for your answers.
Hi copperlanding, No MacOS fix from Apple with recent os releases. Application not notarized as digiKam must be self signed on target computer by hand as explained in this file. This is not a bug from Apple, it's a feature (a regression from me). I refuse to give one cts to Apple, it's must be the inverse. After all we spend a lots of time to support this proprietary OS. Best Gilles Caulier
Hi Michael, If we run the self-signed command directly in the install script from the package, It will work ? As it's said in the open source Package application used to create the MacOS installer : "Support for bundle pre- and post-installation scripts" http://s.sudre.free.fr/Software/Packages/tech_specs.html I have a big doubt here, else this Apple signature to force to pay the notarization will be a non-sense after all as it can be easily by-passed (:=))) Best Gilles
(In reply to caulier.gilles from comment #15) > If we run the self-signed command directly in the install script from the > package, It will work ? As it's said in the open source Package application > used to create the MacOS installer : > > "Support for bundle pre- and post-installation scripts" > > http://s.sudre.free.fr/Software/Packages/tech_specs.html > > I have a big doubt here, else this Apple signature to force to pay the > notarization will be a non-sense after all as it can be easily by-passed > (:=))) There’s no reason self-sign shouldn’t work in the installer script, it will however that the user authorizes the command. The point of notarization isn’t to "extract money" from anyone, but to make sure that someone is responsible for the code and potentially embedded malware, and that means IDENTIFYING the responsible party, which is obviously a costly process. Besides, the $99/year give you full access to developer resources, pre-releases, etc. So hardly the type of money that makes Apple rich. The point of self-signing is exactly to allow the sort thing done here, but it must be done by an admin user, so it once more requires someone to take responsibility for the signature/installation; and that’s the whole point: there’s always someone to point the finger at, if things go bad.
Hi to everyone trying to find a work-around for the issue. Since I (and I guess many others) are no Mac or MacOS experts and not working with "Terminal" on a daily bases: I tried to understand the solution "run command "sudo codesign --force --deep --sign - ./digikam.app" from the ./Applications/digiKam.org folder" but have no clue how this should work. I can enter the above mentioned command in the terminal app but what does it mean"run from the ./Applications/digiKam.org folder."? I would very much appreciate if someone could explain in an easy "non expert" step-by-step way how to execute this solution. Ihave uninstalled DigiKam 8.5.0 and now I am stuck since I am unable to install the latest version... Thanks in advance to everyone who could help. Best regards Frank
Hi Frank, Open Terminal and type this command exactly. This assumes that digiKam is installed in the default location. sudo codesign --force --deep --sign - /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam Cheers, Mike
C. opperlanding wrote: > Hi Mike, > Thanks for your kind answer. No, it did not work unfortunately. Digicam Logo was seen for a millisecond and than the program crashes. I assume I have to stay with version 8.5.0… > Best wishes > Frank PS I cannot send you the error reports since your system allows no answers longer than 65535 characters. Am 23.04.2025 um 15:19 schrieb Michael Miller <bugzilla_noreply@kde.org>: https://bugs.kde.org/show_bug.cgi?id=496380 --- Comment #18 from Michael Miller <michael_miller@msn.com> --- Hi Frank, Open Terminal and type this command exactly. This assumes that digiKam is installed in the default location. sudo codesign --force --deep --sign - /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam Cheers, Mike
P.S. The installation worked with your command but the program crashed mili-seconds after the double-click to open the program. I am lost Frank Am 23.04.2025 um 15:19 schrieb Michael Miller <bugzilla_noreply@kde.org>: https://bugs.kde.org/show_bug.cgi?id=496380 --- Comment #18 from Michael Miller <michael_miller@msn.com> --- Hi Frank, Open Terminal and type this command exactly. This assumes that digiKam is installed in the default location. sudo codesign --force --deep --sign - /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam Cheers, Mike
Please let me know if I can be of help for the error search. Best regards Frank Am 29.04.2025 um 23:18 schrieb C. opperlanding <copperlanding@gmail.com>: P.S. The installation worked with your command but the program crashed mili-seconds after the double-click to open the program. I am lost Frank Am 23.04.2025 um 15:19 schrieb Michael Miller <bugzilla_noreply@kde.org>: https://bugs.kde.org/show_bug.cgi?id=496380 --- Comment #18 from Michael Miller <michael_miller@msn.com> --- Hi Frank, Open Terminal and type this command exactly. This assumes that digiKam is installed in the default location. sudo codesign --force --deep --sign - /Applications/digiKam.org/digikam.app/Contents/MacOS/digikam Cheers, Mike
Git commit e907351be77a9906965876cb4211f3aeb742357c by Gilles Caulier. Committed on 09/05/2025 at 08:19. Pushed by cgilles into branch 'master'. run Apple codesign tool in the post install bash script to fix the "The application dock does not have permission to open (null)" error introduced with macOS 15 Related: bug 496828, bug 497285 FIXED-IN: 8.7.0 M +8 -4 project/bundles/macports/04-build-installer.sh https://invent.kde.org/graphics/digikam/-/commit/e907351be77a9906965876cb4211f3aeb742357c