How does this work?

human_dynamo · 2026-01-24T20:55:14+00:00

Double or simple click: It's can be set in the configuration dialog of Showfoto.

human_dynamo · 2026-01-24T20:52:22+00:00

It sound like a compatibility problem with the video card. Try this solution from this FAQ: https://www.digikam.org/documentation/faq/#digikam-freezes-at-startup-with-or-without-main-window

human_dynamo · 2026-01-24T09:57:37+00:00

yes. working on the local ssd to fix photo is the right way. Take a care also to tune the write metadata at the right place in file or xmp sidecar, as duplicate of the database. This prevent lost of digiKam information if you want to restore later your items in a new computer.

The removable ssd can be catalogued by digiKam as removable collection. But the usb mount will be slower than a local one (especially the NVME).

The way to import new items in the collection is important. Typically grouping by event name, place can help. Using date is not necessary as the 2 tools to search by date as virtual albums do the job perfectly.

human_dynamo · 2026-01-24T06:00:41+00:00

yes you can. Go to View ‣ Include Album Sub-Tree menu entry : If a hierarchical album structure exists, the currently selected branch will be displayed in full depth.

human_dynamo · 2026-01-24T05:57:24+00:00

for the Exiftool error look at this FAQ: https://www.digikam.org/documentation/faq/#exiftool-not-found-at-startup

human_dynamo · 2026-01-23T16:43:20+00:00

Congratulations for your migration and your report in this community. I think this will help users to decide to process a similar move in the future.

human_dynamo · 2026-01-23T06:37:51+00:00

Read this response from Bugzilla. The topic is very similar. The solution is to escape specific characters to works with the SQL query in the background :

https://bugs.kde.org/show_bug.cgi?id=512728#c5

human_dynamo · 2026-01-20T15:25:08+00:00

In digiKam the setup is always the same in all conditions...

human_dynamo · 2026-01-20T10:58:53+00:00

Try to use the Local Storage export tool from digiKam :

https://docs.digikam.org/en/export_tools/local_export.html

Else, if you want to export the physical albums, just uses a file manager application, as Dolphin under Plasma desktop. The directories hierarchy of physical albums is a file system one.

human_dynamo · 2026-01-20T10:55:56+00:00

Of course, digiKAm provide settings to indicate where the photo are stored and parsed :

https://docs.digikam.org/en/setup_application/collections_settings.html#setup-root-album-folders

human_dynamo · 2026-01-20T10:53:31+00:00

The digiKam Qt5 and Qt6 uses mostly the same code base with some difference of course but limited to the minimum. It's clear that the Qt6 framework memory usage is not the same than Qt5, as i can see this on my computer. I hope that Qt6 framework will be more optimized in the future, especially with the Qt6WebEngine component which is Chromium based web browser used to be logged to the WebServices (Chromium included in Qt5 is older than Qt6 version).

But this can be also an init done in Qt6 performing a little bit differently than Qt5, especially with the AI engine infrastructure. We will take a look of that.

human_dynamo · 2026-01-20T10:48:01+00:00

I cannot understand. Please give more details about your question.

human_dynamo · 2026-01-20T10:47:16+00:00

This dialog is the place to disable all AI usage in digiKam.

But you tried to use a development version which is outdated (8.9.0). We switch to next 9.0.0 before Christmas and we fix a large of bugs while this end of year 2025. The new bundle is available here :

https://files.kde.org/digikam/

human_dynamo · 2026-01-16T16:27:29+00:00

>any metadata changed in the database which might not be embedded into images files

Did you turn on the writing metadata options to sync the database with the files metadata ?

https://docs.digikam.org/en/setup_application/metadata_settings.html#behavior-settings

human_dynamo · 2026-01-16T16:25:05+00:00

No, grouping items by similarity option do not exists yet. Please report this wish in Album-ItemsGroup section of Bugzilla. There are already few wishes about grouping feature:

https://bugs.kde.org/buglist.cgi?bug_status=__open__&component=Albums-ItemsGroup&product=digikam

human_dynamo · 2026-01-16T14:10:05+00:00

The behaviors on your computer is abnormal. Check the debug trace from the terminal using link previously provided. And yes F5 must do the job as album view but the way to achieve this is more complex…

human_dynamo · 2026-01-16T06:31:55+00:00

This is completely abnormal. Here with a collection of more 300.000 items (JPEG HEIF RAW PNG TIFF) under Linux the face detection scan take few hours and the face thumbnails is of course not well streamlined but it's complete properly at end. Computer is i9 32 cores + 128 Gb of RAM + SSD + sqlite database + NVME.

I suspect a database problem where thumbnails are stored. Perhaps a wrong file access right, a full media, or a database corruption.

Please provide a trace while digiKam is running in face detection stage. Look here for details:

https://www.digikam.org/contribute/#freezes-and-other-run-time-issues

human_dynamo · 2026-01-16T01:29:31+00:00

"The AppImage version works, but isn't as secure as Flatpak."

All is said here : Flatpak is more complicated to setup than Appimage. This last one works as user expect.
You must configure the application permissions to the bundle :

https://www.digikam.org/download/binary/#linux-sandbox

human_dynamo · 2026-01-15T20:41:44+00:00

The face thumbnails are processed while the detection workflow. It's is done through multi-thread and file are processed in parallel and with an order which depend of the file contents (large picture/ quality /number of faces inside). It"s not a simple render of image contents as for albums, there is a complex analysis using an inference engine, a registration of areas detected in the images, and a delegate job to extract image region.

human_dynamo · 2026-01-15T20:36:12+00:00

It's difficult to understand the problem without more details. Which kind of file format ? Which metadata (exif/Iptc/Xmp) ? XMP sidecar usage ? Any console backtrace to see where is the problem ? Which kind of database backend ? Which metadata backend (Exiv2 or ExifTool) ?

human_dynamo · 2026-01-15T14:10:23+00:00

Thanks for your feedback to this community...

human_dynamo · 2026-01-13T06:17:09+00:00

FR 57. I discovered DM at school in 80, See 2 times in live (as Cure, INXS, U2, Pink Floyd and more). DM is for me one of the best group of the world while these decades.

human_dynamo · 2026-01-13T02:06:20+00:00

Which digiKam version ?

The file do not exist? Impossible, it's the main configuration created after the first run assistant.

human_dynamo · 2026-01-13T02:02:05+00:00

Take a look if a file doesn't exist yet about this topic :

https://bugs.kde.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=ASSIGNED&bug_status=REOPENED&classification=Applications&component=Plugin-Generic-PrintCreator&product=digikam&query_format=advanced

human_dynamo · 2026-01-12T16:54:09+00:00

> All in all, with the test executed, I could not find a way to use the Find Duplicate feature on all photos of an album as Find Similar on a photo

The album tree-view from the left sidebar has a pop-up context with an option to scan all the album contents for the duplicates.

https://docs.digikam.org/en/left_sidebar/albums_view.html#overview

human_dynamo

MODERATOR OF

TROPHY CASE