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

I updated my openSUSE system to the latest version. Now I have the same=20
problem. Upon investigation, we find that the SQL driver is already returni=
ng a=20
QVariant containing an invalid QDateTime. It therefore appears to be a bug =
in=20
the MariaDB connector. This might be the corresponding bug report.

https://jira.mariadb.org/projects/CONC/issues/CONC-821?filter=3Dallopenissu=
es

Maik

Am Samstag, 18. Juli 2026, 07:35:24 Mitteleurop=C3=A4ische Sommerzeit schri=
eb VAL=C3=8DK=20
Robert:
> Sorry, attaching now.
>=20
> 1. started Digikam, let the scan run for a few seconds
> 2. cancel the index
> 3. refresh Photos-Import/2026/20260704
> 4. refresh Photos-Import/2026/20260704 second time
> 5. refresh Photos-Import/2026 - and the "Find new items" stays at 0%=20
> (watching the logs - it reread [and rewrote the data in DB] the first=20
> folder 20260101 quickly than paused for like a minute and continued after)
> 6. I then aborted the refresh, digikam shows "No active process" but the=
=20
> output and MariaDB binlog show that it still runs and scans... Stops=20
> after I close digikam.
>=20
> Than I started digikam again and the full scan and rewrite of data in=20
> the DB start again...
>=20
> If you need the full scan to finish, I can let it run during the night=20
> (but already did that a few times with no change).
>=20
> Robert
>=20
> On 7/17/26 20:11, Maik Qualmann wrote:
>=20
> > The AppImage log looks fine so far, aside from the fact that the color
> > profile
 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
 for terminal output.
> >
> >
> >
> > Maik
> >
> >
> >
> > Am Freitag, 17. Juli 2026, 09:17:17 Mitteleurop=C3=A4ische Sommerzeit s=
chrieb
> > VAL=C3=8DK
 Robert:
> >=20
> >> Hello,
> >>
> >>
> >>
> >> the 9.2.0 debug AppImage does not show the weird behavior. It correctly
> >> starts, scans for new items for a fraction of a second and is done. I
> >> also tried to refresh one existing folder and it was immediate without
> >> rewriting all  image metadata data (logs attached) to the DB like the
> >> Arch extra/digikam 9.1.0-6 does.
> >>
> >>
> >>
> >> Robert
> >>
> >>
> >>
> >> On 7/16/26 06:39, Maik Qualmann wrote:
> >>
> >>
> >>
> >>> 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
> >>> schrieb
> >>> VAL=C3=8DK
> >>>=20
> >   Robert:
> >  =20
> >>>> No,
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> a) that disables the whole functionality - detecting new items and
> >>>> albums
> >>>> in
> >  =20
> >   the collection b) as I regularly create new albums (folders) I
> >  =20
> >>>> cannot refresh them as they do not exist in Digikam. I have to refre=
sh
> >>>> 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 existi=
ng
> >>>> image in tget path gets scanned again and it=E2=80=99s metadata (abd
> >>>> thumbnail)
> >>>> are rewritten 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:
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> =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 tr=
ee
> >>>>> opened from the left edge controls.  That only scans the selected
> >>>>> album
> >>>>> for new items.  Does that work for you?
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Cheers, Rainer
> >>>
> >>>
> >>>
> >>>
> >>>
> >> --=20
> >> *Robert Val=C3=ADk*
> >> https://robert.valik.sk/
> >>
> >>
> >>
> >> Sent from my MUA
> >
> >
> >
> >
>=20
> --=20
> *Robert Val=C3=ADk*
> https://robert.valik.sk/
>=20
> Sent from my MUA