"scan for new items" always scans the entire collection

[Charlie Gorichanaz]

I think I may have been noticing this excessing rescanning as well as
another problem related to timestamps but haven't had any time to debug:
Sorting by camera date completely stopped working for me recently and the
dates disappeared from the listing screen, but the metadata is fine for the
photos, similar to this Reddit post:
https://www.reddit.com/r/digiKam/comments/1q3yqrg/exif_date_created_not_shown_in_digikam/
The lack of people reporting this made me think it must be something
particular to my setup or that I messed up, hence waiting to say anything.
Then I discovered launching the AppImage instead of the native Arch Linux
package solved that problem, but I'm not sure about the rescanning issue. I
have been meaning to sit down and figure out what's going on!

—
Charlie Gorichanaz


On Wed, Jul 8, 2026 at 10:34 PM VALÍK Robert <robert at valik.sk> wrote:

> Hey there!
>
> After upgrading Digikam to version 9.1, I have also noticed this weird
> behavior.
>
> I have:
>
> - EndeavourOS
> - extra/digikam 9.1.0-4 (32.9 MiB 115.2 MiB) (Installed)
> - MariaDB server as a backend
>
> Config:
>
> - "Scan for new items at startup" on
> - "Fast Scan (...)" on
>
> I have had this configuration for years (the Digikam DB may have worked
> and been upgraded for about 10 years). Up until upgrade - every time I
> have started Digikam, it scanned briefly (like seconds) for new items,
> if there were new items, it imported them (few seconds or minutes) and
> so.
>
> But after upgrading, it scans and updates the entire collection every
> time. It takes more than 8hrs. Digikam rewrites all data stored in the
> database. It creates like 3GB of binlogs every time. If I log queries,
> it literally checks timestamp of a picture and than deletes and writes
> it's metadata (and thumbnails) all over again. After it finishes and I
> close it and start again, it happens again.
>
> I have tried every DB maintenance option I have found in Digikam, still
> not working properly.
>
> The only thing that did help - was to migrate the DB to SQLite (this is
> complicates things for me, as I synchronize images and metadata from
> Digikam to my webpage and SQLite cannot be as effectively backed up as
> MariaDB...).
>
> It seems like Digikam may not be handling timestamps stored in MariaDB
> properly and decides that the metadata meed to be updated or something.
>
> Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20260709/cac3ba3d/attachment.htm>