https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #8 from Urs Fleisch ---
I finally managed to build signed an notarized packages for both the arm64 and
x86_64 via the KDE CI/CD infrastructure. Could you please check if
kid3-git20240810-Darwin-arm64.dmg and kid3-git20240810-Darwin-amd64.dmg
https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #7 from Urs Fleisch ---
There is now a link to a signed package for ARM64 Apple Silicon on the Kid3
Homepage, see https://invent.kde.org/multimedia/kid3/-/issues/573.
--
You are receiving this mail because:
You are watching all bug changes
https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #6 from J.F.Lanting ---
The "Open Anyway" button no longer exists in Big Sur .
I will stick to 3.8.7 till I must switch to Silicon hardware.
;JOOP!
On 29/12/2021 14:11, Urs Fleisch wrote:
> https://bugs.kde.org/show_bug.cgi?id=447441
>
https://bugs.kde.org/show_bug.cgi?id=447441
Urs Fleisch changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #4 from J.F.Lanting ---
This is all going above my head;
I'll leave it to more experienced users to do the research.
Btw.: Big Sur did not give me any chance to allow the open;
it said "Bin or cancel".
I'll await the future events.
Happy 202
https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #3 from Urs Fleisch ---
I am glad that you like Kid3. Did you have the opportunity to check whether the
other two packages I mentioned have the same problem? Also I have not heard
before that it is no longer possible to run an unsigned app b
https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #2 from J.F.Lanting ---
Kid3 is a great program and I'm satisfied with 3.8.7
You should be aware that MacOS is the safest OS and that the rules
will be tightened from day by day to keep it safe.
So, I expect that you will start to sign futur
https://bugs.kde.org/show_bug.cgi?id=447441
--- Comment #1 from Urs Fleisch ---
Kid3 was never signed, neither 3.9.0, nor 3.8.7 nor any older release, so it
does not make sense why it should be refused to open on macOS 11.6.2. Maybe
this is a false positive detection of macOS.
You could try the
