As this is your first install, I don’t see any point in trying further debugging (config removal) and it looks like you are experiencing a bug with the mac bundle - this is a bit surprising, as I thought there’s quite a few mac users out there. Can you open a bug report with the screenshots and informations about your system and how you installed (in case you didn’t use the installer provided on digikam.org): Log in to KDE Bugtracking System
What happens if you press “Ctrl+Shift+,”? That’s the shortcut for configure digikam.
I volunteered to help improving the handbook but apparently I am not doing a good job here. I do try to add/fix one or two things here and there but my life has been too busy lately.
If you know anyone who might interested in contributing please let me know.
Is there a menu called Program or Tools in your global menu? I am not sure how exactly it is called but every program on Mac has it. I would expect it to be one of the first ones on the left.
OK I think I have found Configure: it is under the menu digiKam → Preferences. When I select that, a box opens up with the heading “Configure” (not Preferences).
Great product, great improvements, and I would love this one as well, except I cannot get it to open.
It launches and brings up a scanning collections window, get to about 54% and vanishes. Never goes any further.
Ideas?
The best way to see what is going on would be to download and install Microsoft DebugView, launch it and then launch digiKam.
digiKam will be printing a bunch of stuff there, please pay attention to what is happening in there when digiKam stalled. I bet it has something to do with certain files or file types being added to the database.
I believe the bundle for windows of digikam already contains a debug library, which produces a log on crash at C:\Users\_user_name_\AppData\Local\digikam_crash.log.
I believe digiKam 6.0.0 does produce crash logs but only on crash though. There is no terminal built-in to see what is happening in the background. Linux and Mac OS have terminal. Windows users need to use DebugView or something of the sort (command line or power shell won’t help).
Here a link to DebugView: