After upgrading to DK 8.6 no images can be opened in my collection

[Thomas]

Hi,

I don't understand. Are you saying that the problem here is that since 
DK is not distributed as a signed/notarized package, DK will not be able 
to work anymore on MacOS?


A few questions:

1: Why does it work when logging is enabled?

2: Is there no workaround to this?

3: Why did this work in previous versions of DK? Or is this just a 
coincidence that my upgrading DK happens almost same time as I updated 
MacOS - and update to MacOS is the real issue?

4: Regarding costs, have you reached out to Apple to apply for an 
exemption?

5: What do other open source projects to do overcome this obstacle?

6: Will this mean that from now on, DK will not be usable on MacOS?


BR

Thomas



On 02/04/2025 12.55, Gilles Caulier wrote:
> Welcome to the MacOS world with the regression introduced by Apple 
> with last MacOS version.
>
> Look in this file from Bugzilla :
>
> https://bugs.kde.org/show_bug.cgi?id=453078
>
> This one is nice too, as the digiKam PKG is not notarized with the 
> Apple workflow.
>
> https://bugs.kde.org/show_bug.cgi?id=496380
>
> The cost is 100€ per year. It's a shame. I REFUSE to give 1cts to 
> Apple for an OpenSource project.
> Apple must pay the developers to build applications for MacOS (I'm 
> Apple fan and user anyway).
>
> Best
>
> Gilles Caulier
>
>
> Le mer. 2 avr. 2025 à 10:43, Thomas <sdktda at gmail.com> a écrit :
>
>     So, this is quite strange. And I had to check this several times
>     to make
>     sure it was not me turning senile.
>
>     When I enable logging, the problem is gone: DK opens images from the
>     collection just fine.
>
>     However, if I start DK using the Dock icon, then it gives me the
>     error
>     when opening an image.
>
>     How can this be?
>
>
>     I will send you the log separately.
>
>
>     BR
>
>     Thomas
>
>
>     On 01/04/2025 20.44, Maik Qualmann wrote:
>     > This UUID file can be used by all clients; we only had a bug
>     with a 8.x.x
>     > version where we kept creating a new UUID. This UUID has been
>     used since
>     > digiKam-8.x.x to reliably identify a collection. What version
>     did you upgrade
>     > from to digiKam-8.6.0?
>     > It's actually quite easy to get the collection back online, but
>     I would like
>     > to see a log from the terminal when digiKam starts up to
>     identify the exact
>     > problem. Please create the log:
>     >
>     > https://www.digikam.org/contribute/#macos-host
>     >
>     > Maik
>     >
>     > Am Dienstag, 1. April 2025, 20:35:10 Mitteleuropäische
>     Sommerzeit schrieb
>     > Thomas:
>     >> I still have the .dtrash folder.
>     >>
>     >> It contains .dtrash/digikam.uuid as well as a lot of
>     >> .dtrash/info/*-*.dtrashinfo files.
>     >>
>     >>
>     >> Please note that this collection is shared across multiple client
>     >> machines with DK on them. Several Macs, Linux and Windows clients.
>     >>
>     >> I was not aware there was some UUID in there. Is this not
>     supposed to be
>     >> shared?
>     >>
>     >> Is this perhaps related to the problems I have? I have run this
>     setup
>     >> for like 15-20 years without problems....
>     >>
>     >> On 01/04/2025 20.14, Maik Qualmann wrote:
>     >>> Did you perhaps delete the hidden .dtrash folder in the root
>     of your
>     >>> network folder? Is it still there and does it contain a file named
>     >>> "digikam.uuid"?
>     >>>
>     >>> Maik
>     >>>
>     >>> Am Dienstag, 1. April 2025, 19:41:03 Mitteleuropäische
>     Sommerzeit schrieb
>     >>>
>     >>> Thomas:
>     >>>> On 2025-04-01 18.57, Hans-Peter Huth wrote:
>     >>>>> We need more info. Which Operating system, if Linux, is it
>     an official
>     >>>>> Appimage, natively provided by the distribution, flatpak,
>     snap? I
>     >>>>> suggest,
>     >>>>> try the appimage.
>     >>>> Good point!
>     >>>>
>     >>>> OS is MacOS.
>     >>>>
>     >>>> Hardware is MBP M3.
>     >>>>
>     >>>> DK is downloaded from the website. Installed using the installer.
>     >
>     >
>     >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20250402/b2ee3ecb/attachment.htm>