<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Yes, that is everything I got. After the last entry, it hangs forever (or until I manually stop the process).</div><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""></div></div></div>MacOS version: 12.6.5 (21G531)</div><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""></div><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Dominik</div></div><div class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""></div></div></div></div><div><blockquote type="cite" class=""><div class="">On 16. May 2023, at 09:48, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" class="">caulier.gilles@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">And it's all... ?<br class=""><br class="">Mine is very similar but it continues so far. I cannot see any dysfunction here.<br class=""><br class="">Which MacOS version did you use exactly ?<br class=""><br class="">Gilles Caulier<br class=""><br class="">Le mar. 16 mai 2023 à 09:11, Dominik Austen <<a href="mailto:Dominik.austen@web.de" class="">Dominik.austen@web.de</a>> a écrit :<br class=""><blockquote type="cite" class=""><br class="">Hi,<br class=""><br class="">No, I am not using digikam in any of these situations. The digikam database folder is on the internal drive and ca. 20MB of size. Except for the startup wizard (when the digikamrc is removed), no other window is displayed.<br class=""><br class="">I installed the new 8.1.0 version, unfortunately no change.<br class=""><br class="">I attached the full debug trace (with v8.1.0)<br class=""><br class="">Dominik<br class=""><br class=""><br class=""><br class=""><br class="">On 16. May 2023, at 07:54, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" class="">caulier.gilles@gmail.com</a>> wrote:<br class=""><br class="">Hi,<br class=""><br class="">Also another possible way to generated full debug trace on the<br class="">Terminal, is to process like this :<br class=""><br class="">bash-3.2$ pwd<br class="">/Applications/<a href="http://digiKam.org/digikam.app/Contents/MacOS" class="">digiKam.org/digikam.app/Contents/MacOS</a><br class="">bash-3.2$ export QT_LOGGING_RULES="*=true"<br class="">bash-3.2$ ./digikam<br class=""><br class="">...<br class="">digikam.qtav: Register QtAV Renderers:<br class="">digikam.qtav: Qt have no OpenGL support.<br class="">digikam.qtav: register QtAV::OpenGLWidget Renderer: true<br class="">digikam.qtav: QtAV have OpenGL support.<br class="">digikam.qtav: register QtAV::QGLWidget Renderer: true<br class="">digikam.qtav: register QtAV::QGLWidget2 Renderer: true<br class="">digikam.qtav: register QtAV::Widget Renderer: true<br class="">digikam.qtav: register QtAV::GraphicsItem Renderer: true<br class="">qt.qpa: Loading macOS (Cocoa) platform plugin for Qt 5.15.8, running<br class="">on macOS 12.6.3<br class=""><br class=""> Component SDK version Deployment target<br class="">------------- ------------- -------------------<br class=""> Qt 5.15.8 13.1.0 10.15.0<br class=""> Application 12.3.0 10.15.0<br class=""><br class="">qt.qpa.screen: Updating screens with 1 online displays: QVector(69733312)<br class="">qt.qpa.screen: Adding QCocoaScreen(0x600002c0a080, "Colour LCD",<br class="">QRect(0,0 1440x900), dpr=2, displayId=69733312, <NSScreen:<br class="">0x6000039237e0>) as new primary screen<br class="">qt.qpa.openglcontext: Failed to create NSOpenGLContext<br class="">qt.qpa.openglcontext: Failed to create NSOpenGLContext<br class=""><br class="">This will open the door to Qt framework used by digiKam to print all<br class="">debug traces on the Terminal. It's very verbose. Please capture the<br class="">text and report in ths room.<br class=""><br class="">Best<br class=""><br class="">Gilles Caulier<br class=""><br class="">Le mar. 16 mai 2023 à 07:49, Gilles Caulier <<a href="mailto:caulier.gilles@gmail.com" class="">caulier.gilles@gmail.com</a>> a écrit :<br class=""><br class=""><br class="">Hi,<br class=""><br class="">The new 8.1.0 PKG installer for MacOS using Exiv2 0.28 is available here :<br class=""><br class=""><a href="https://files.kde.org/digikam/" class="">https://files.kde.org/digikam/</a><br class=""><br class="">Best regards<br class=""><br class="">Gilles Caulier<br class=""><br class="">Le mar. 16 mai 2023 à 05:28, Gilles Caulier <caulier.gilles@gmail.com> a écrit :<br class=""><br class=""><br class="">Also, The PKG MacOS installer 8.1.0 pre-release will be compiled soon<br class="">with the new Exiv2 0.28 release which includes a large list of fixes:<br class=""><br class="">https://github.com/Exiv2/exiv2/issues/2406#issuecomment-1529139799<br class=""><br class="">ExiV2 is used in the background to populate the database with files metadata.<br class=""><br class="">Gilles Caulier<br class=""><br class="">Le mar. 16 mai 2023 à 05:23, Gilles Caulier <caulier.gilles@gmail.com> a écrit :<br class=""><br class=""><br class="">Hi,<br class=""><br class="">Are you using digiKam in these kind of situations already reported in bugzilla ?<br class=""><br class="">https://bugs.kde.org/show_bug.cgi?id=367853<br class="">https://bugs.kde.org/show_bug.cgi?id=367979<br class="">https://bugs.kde.org/show_bug.cgi?id=457476<br class=""><br class="">Gilles Caulier<br class=""><br class="">Le lun. 15 mai 2023 à 16:59, Dominik Austen <Dominik.austen@web.de> a écrit :<br class=""><br class=""><br class="">yes, I am also admin.<br class=""><br class="">Dominik<br class=""><br class=""><br class=""><br class=""><br class="">On 15. May 2023, at 16:22, Gilles Caulier <caulier.gilles@gmail.com> wrote:<br class=""><br class=""><br class=""><br class="">Le lun. 15 mai 2023 à 14:14, Dominik Austen <dominik.austen@web.de> a écrit :<br class=""><br class=""><br class="">Hi Gilles,<br class=""><br class="">thank you for your response!<br class="">Unfortunately, I am not able to set the right configurations as indicated in the documentation. Digikam is not listed under any panels in the Privacy tab in the System Preferences/Security&Privacy. I am able to add digikam manually via the “+” button, but only for Full Disk Access and Accessiblity, not for Automation or Photos. I restarted digikam and the computer but so far without any success. Is there another way to grant digikam the necessary rights?<br class=""><br class="">Dominik<br class=""><br class=""><br class=""><br class=""><br class="">Well I’m admin on my MacBook computer. It’s the same for you ?<br class=""><br class="">This can make a difference at run time.<br class=""><br class="">Gilles<br class=""><br class=""><br class=""><br class=""><br class="">On 15. May 2023, at 12:52, Gilles Caulier <caulier.gilles@gmail.com> wrote:<br class=""><br class="">Hi,<br class=""><br class="">I have seen a similar problem in the past on my macbook pro 2015 intel<br class="">running Monterrey. The problem is about the access rights to turn on<br class="">for the application.<br class=""><br class="">Typically, MacOS must ask to give rights through a dialog box, but<br class="">sometime now. You need to set up these configurations in the MacOS<br class="">control panel. See the Online documentation for details:<br class=""><br class="">https://docs.digikam.org/en/getting_started/installation.html#application-rights<br class=""><br class="">About the Q "why digiKam do not apply the rights automatically on<br class="">MacOS", in fact it's due to the security policy from Apple. This kind<br class="">of rule works if the application is signed, but of course you need to<br class="">pay a developer account to Apple, and we refuse to give money to a big<br class="">high tech company for an open source project as digiKam. This must be<br class="">the inverse in theory...<br class=""><br class="">Best<br class=""><br class="">Gilles Caulier<br class=""><br class="">Le lun. 15 mai 2023 à 11:37, Dominik Austen <Dominik.austen@web.de> a écrit :<br class=""><br class=""><br class="">Hi all,<br class=""><br class="">I just installed DigiKam, but it does not start properly on my Mac.<br class="">I am able to go through the startup assistent without any issues. But when I click on “Finish” on the “Scan your Collection” page, the window disappears and nothing happens. When I click on the icon in the Dock, it says: “Application Not Responding”. After forced quitting and restarting, the application is instantly not responsive without showing any window.<br class=""><br class="">The symptoms are somewhat identical to the last comment in Bug 463536 on the KDE Bugtracking System, which did not get any further answers.<br class=""><br class="">Specifications:<br class="">Processor: Intel<br class="">OS: MacOS 12.6.5 (Monterey)<br class="">DigiKam-Version: 8.0.0 (same problem occurs with 7.10)<br class=""><br class="">I attached the terminal output.<br class=""><br class="">Dominik<br class=""><br class=""><br class=""><br class=""><br class="">--<br class="">Send with Gmail Mobile<br class=""><br class=""><br class=""><br class=""></blockquote></div></div></blockquote></div><br class=""></body></html>