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

The AppImage log looks fine so far, aside from the fact that the color prof=
ile=20
isn't being detected=E2=80=94though that=E2=80=99s a separate issue.
Why isn't there a log from your Arch version? A debug build isn't necessary=
=20
for terminal output.

Maik

Am Freitag, 17. Juli 2026, 09:17:17 Mitteleurop=C3=A4ische Sommerzeit schri=
eb VAL=C3=8DK=20
Robert:
> Hello,
>=20
> the 9.2.0 debug AppImage does not show the weird behavior. It correctly=20
> starts, scans for new items for a fraction of a second and is done. I=20
> also tried to refresh one existing folder and it was immediate without=20
> rewriting all  image metadata data (logs attached) to the DB like the=20
> Arch extra/digikam 9.1.0-6 does.
>=20
> Robert
>=20
> On 7/16/26 06:39, Maik Qualmann wrote:
>=20
> > 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
> > 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 s=
chrieb
> > VAL=C3=8DK
 Robert:
> >=20
> >> No,
> >>
> >>
> >>
> >> a) that disables the whole functionality - detecting new items and alb=
ums
> >> 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 t=
humbnail)
> >> are rewritten c) I do import photos from different sources and differe=
nt
> >> dates so it is quite impossible to know every folder I should refresh
> >>=20
> >>> On 9 Jul 2026, at 20:34, Rainer J.H. Brandt<[email protected]> wrote:
> >>>
> >>>
> >>>
> >>> =EF=BB=BFDiego writes:
> >>>=20
> >>>> In our case (no faces involved), "scan for new items" should only sc=
an
> >>>> 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 alb=
um
> >>> for new items.  Does that work for you?
> >>>
> >>>
> >>>
> >>> Cheers, Rainer
> >
> >
> >
> >
>=20
> --=20
> *Robert Val=C3=ADk*
> https://robert.valik.sk/
>=20
> Sent from my MUA