Summary: | “kmymoney.app” is damaged and can’t be opened. You should move it to the Trash. | ||
---|---|---|---|
Product: | [Applications] kmymoney | Reporter: | theUser <douglas5200> |
Component: | packaging | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
Status: | REPORTED --- | ||
Severity: | grave | CC: | douglas5200, jonathan, mermuirhead, nate, ralf.habacker |
Priority: | NOR | ||
Version First Reported In: | 5.1.0 | ||
Target Milestone: | --- | ||
Platform: | macOS (DMG) | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Error message |
Description
theUser
2024-05-24 23:52:37 UTC
> spctl --assess -vv /Applications/kmymoney.app
/Applications/kmymoney.app: a sealed resource is missing or invalid
> xattr -p com.apple.quarantine /Applications/kmymoney.app 0183;66511eb3;Safari;A2DB7A60-E0A4-42C8-8233-6DF1AFD064C2 > xattr -d -r com.apple.quarantine /Applications/kmymoney.app Now the application launches successfully, but why? I don't think anyone on the KMM team is a Mac user. Since you have it working, I suspect an answer as to why what you did helped will need to come from a Mac related list or forum. I'll probably close as DOWNSTREAM, but if you do find anything that might be changed in the build or packaging process, let us know. However, given that the current stable builds for Max x86-64 are not working (see https://kmymoney.org/macos.html) and the version for arm64 is from March, I'm not sure when will will be able to use such information for a new build. I had a problem on Sonoma with kMymoney, the problem was alleviated by static linking. Not all extensions can use static linking so this is a cut down version which is still too large to attach, so a download link is provided below at your own risk: https://jonathankimmitt-my.sharepoint.com/:u:/g/personal/jonathan_kimmitt_uk/EeAVhWVp4pRNvEXrNgvrueAB6mSqJSnV4-OTGa3A4L-UBg?e=BUu4EI (In reply to Jonathan Kimmitt from comment #4) > I had a problem on Sonoma with kMymoney, Please open a separate entry for this problem, as it has nothing to do with the problem described here. *** Bug 496750 has been marked as a duplicate of this bug. *** |