| Summary: | Cannot start app under MacOS Intel: The application dock does not have permission to open (null) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | alexkrz <alex.kurz95> |
| Component: | Bundle-MacOS | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | major | CC: | caulier.gilles, mark.christensen, michael_miller, pbcachim, rcfa+kde.org |
| Priority: | NOR | ||
| Version: | 8.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | macOS (DMG) | ||
| OS: | macOS | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
alexkrz
2024-11-17 15:51:54 UTC
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. *** |