Very slow to open

Hey there, I’m running an M4 Mac Mini, with MacOS 27.0.1. Recently I’ve noticed, when opening Digikam, that it can take up to 20-30 seconds to open. Even then, when it does open, I see the base theme, and then my chosen theme applied on top of it.

Does anyone have an idea what might be causing the lag?

Can I bump this, in the hope that someone might have an idea what’s going on?

I can only say, mine is very slow to open as well, on MacOS, too.

So much so in fact, that I’m now using FerrumPix for browsing. I still use DigiKam for face tagging, but that usage is waning.

Do you have it configured to search your files for updates when starting? I think this is what makes it so slow.
It got significantly faster for me, when I moved from a HDD to an SSD. It still takes quite a long time to start for me as well, thought.

Hey buddy,

Nope, this has been disabled, and I am already using an SSD. Maybe it’s time to look for another DAM.

@bastibe - I looked at FerrumPix, and it looks incredibly similar to an app called LAP. I wonder if they have both been vibe-coded.

The only thing stopping me from using LAP, actually, is that it currently does not read XMP data. Otherwise, it would be a solid solution

Hello, I noticed that some settings do influence the startup time a lot.

Go to Settings, Configure digikam, tab Miscellaneous > Appearance

Select Show splash screen + Widget style Windows + Icon theme Adwaita > startup time is 24 seconds.

No Splash screen + Windows + Adwaita > 22 seconds

No Splash screen + Fusion + Use icon theme from system > ~10 seconds.

This is on a new nvme drive. On my old pc with a ssd, digikam always took some 35 seconds to start. I used to say “The slowest kid on the block”. :upside_down_face:

3 Likes

Hi,

thanks, Digikam now start in 3.82 seconds (was about 5 seconds)!

1 Like

You must have a very good pc $$$ :upside_down_face:

Hm, unfortunately, it doesn’t make a difference for me.
I did note, though, that the very first time I start it takes longer (i.e. start, close, start again; second start will be faster). Probably due to some caching. So make sure to use the time measured during the second start for reference.

I tried now and even disabling “scan for new items at startup” only saves a second or so. Still needs ~15 seconds to start. I really wonder why now.

Thanks, I didn’t think the splash screen would matter, but it got the startup time from 12 to 8 seconds for me. I’m running the AppImage and have been wondering why it’s loading so slow - yes, I tried to disable the “scan for new items” option. The bug tracker didn’t really give any hints nor starting the AppImage from terminal.

-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
--        to extract the bundle contents locally, use option '--appimage-extract' on the command line.
-- Detected host Linux Pop-64-24.04
-- AppImage mounted directory: /tmp/.mount_showfoUmcmOA
Preloading skipped for libudev.so.0
Preloading             /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
Preloading skipped for libcrypto.so.1.1
Preloading skipped for libssl.so.1.1
Preloading             /usr/lib/x86_64-linux-gnu/libnss3.so
Preloading             /usr/lib/x86_64-linux-gnu/libnssutil3.so
Preloading             /usr/lib/x86_64-linux-gnu/libsmime3.so
Preloading             /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
Preloading skipped for libgnutls.so.30
Preloading             /usr/lib/x86_64-linux-gnu/libnettle.so.8
-- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-linux-gnu/libnettle.so.8
unknown: Could not find the Qt platform plugin "wayland" in ""
unknown: Using Qt multimedia with FFmpeg version 8.0.1 nonfree and unredistributable
unknown: Unable to handle language from dictionary "gug" "C"
unknown: Unable to handle language from dictionary "kmr_Latn" "C"
unknown: Unable to handle language from dictionary "ko_KR" "ko_KR"
unknown: QSvgHandler: Image filename is empty
unknown: QSvgHandler: Image filename is empty
unknown: QObject::connect: No such slot Digikam::SurveyWindow::slotDeleteFinalItem() in /dktemp/digikam-v9.1.0/core/utilities/survey/surveywindow_setup.cpp:68
unknown: QObject::connect:  (receiver name: 'Survey')
unknown: Unhandled container to remove :  Digikam::DigikamApp
unknown: QSvgHandler: Image filename is empty
unknown: QSvgHandler: Image filename is empty

Hi,

Not that expensive. In 2025, before the surge in component prices, it cost about half the price of a gaming laptop.
It was built by a local craftsman to my specifications.
I was aiming for longevity, given the way photography software is evolving.

1 Like

Same problem here with Digikam version 9.1.0-1.fc44 on a Laptop with:

Operating System: Fedora Linux 44
KDE Plasma Version: 6.8.2
KDE Frameworks Version: 6.31.0
Qt Version: 6.11.2
Kernel Version: 7.2.14-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen AI 9 HX 370 w/ Radeon 890M
Memory: 32 GB of RAM (30,5 GB usable)
Graphics Processor: AMD Radeon 890M Graphics

VERY slow to start. I don’t remember it being so slow when I first installed it.

Takes 10+ seconds to start, without scanning for changes and without splash screen. On that machine, it shouldn’t take more than 2 seconds IMHO.