Re: "scan for new items" always scans the entire collection

Maik Qualmann <[email protected]> Thu, 16 Jul 2026 06:39:01 +0200
Newsgroups gmane.comp.kde.digikam.user
Message-ID <[email protected]>
Please test the digiKam 9.2.0 pre-release version available here:

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

It includes debug code to investigate the issue further. Please post a log=
=20
from a digiKam startup that includes a scan, as described here:

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

Maik

Am Freitag, 10. Juli 2026, 07:02:28 Mitteleurop=C3=A4ische Sommerzeit schri=
eb VAL=C3=8DK=20
Robert:
> No,
>=20
> a) that disables the whole functionality - detecting new items and albums=
 in
> the collection b) as I regularly create new albums (folders) I cannot
> refresh them as they do not exist in Digikam. I have to refresh the whole
> subtree (folder above them) to let Digikam detect them and it takes almost
> an hour and the result is almost the same, every existing image in tget
> path gets scanned again and it=E2=80=99s metadata (abd thumbnail) are rew=
ritten c)
> I do import photos from different sources and different dates so it is
> quite impossible to know every folder I should refresh
> > On 9 Jul 2026, at 20:34, Rainer J.H. Brandt <[email protected]> wrote:
> >=20
> > =EF=BB=BFDiego writes:
> >> In our case (no faces involved), "scan for new items" should only scan
> >> new items; without this option checked, it should scan the entire
> >> collection. The problem reported here (for DK 9.1.0) is that regardless
> >> of whether you ask to "scan for new items" or not, it will scan the
> >> entire collection. This is not the expected behavior.
> >=20
> > I use the "Refresh" item of the album context menu, in the album tree
> > opened from the left edge controls.  That only scans the selected album
> > for new items.  Does that work for you?
> >=20
> > Cheers, Rainer