Bug 465652

Summary:	Rescan activated for all collection when adding new collection
Product:	[Applications] digikam	Reporter:	tuomas.koponen
Component:	Database-Scan	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	7.9.0
Target Milestone:	---
Platform:	macOS (DMG)
OS:	macOS
Latest Commit:		Version Fixed In:	8.5.0
Sentry Crash Report:
Attachments:	attachment-356148-0.html

Description tuomas.koponen 2023-02-13 07:08:08 UTC

SUMMARY
I do have a collection or roughly 80 000 photos that are kept under NAS device (Nextcloud with webdav via mountainduck). I'm in the middle off consolidating all my external disks to single storage and plugged new external disk and added it as a new collection. At the same time my network disk was mounted from wrong folder (bug by mountainduck, bookmark had subpath defined). Right after I finished to add new external disk all my photos from NAS device was removed.

I have configured Digikam not to scan any files automatically and I have not selected collections to monitor for changes.

STEPS TO REPRODUCE
1. add new collection

OBSERVED RESULT
All collections were rescanned

EXPECTED RESULT
Only added collection to be scanned

SOFTWARE/OS VERSIONS
Windows:
macOS: 13.2 (22D49)
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:

ADDITIONAL INFORMATION
This is not such huge issue as it is recoverable by scanning files again. It will take easily a full day to san 930Gb of images and some videos.

Digikam has worked out well and I do now have rather decent workflow with Piwigo to send images and organise them without Apple or Google services. Only annoyance is this collection management that seems to break rather easily. This was not first time I have had the same. I was hoping that mountain duck would solve some of the issues, but it seems not to be perfect.

I would just hope that I could manage how and when collections are scanned to avoid this kind of a problems. Now settings that exists does not seem to allow that.

Comment 1 caulier.gilles 2023-05-03 04:00:41 UTC

@tuomas.koponen@me.com

digiKam 8.0.0 is out. This entry still valid with this release ?

Best regards

Gilles Caulier

Comment 2 tuomas.koponen 2023-05-03 07:00:51 UTC

Hi, thanks for contacting. I did now Install 8.0.0 I was unable to upgrade due some error with database. I did try to remove all settings, but in all cases using old database folder was no go.

I will now re read all images and then I'm able to test what happens when collections are modified. This will take at least a day.

Comment 3 caulier.gilles 2023-10-19 12:46:40 UTC

@tuomas.koponen@me.com,

digikam 8.2.0 pre-release have been rebuilt using last Qt 5.15.11 + KDE 5.110
frameworks. Installer is available at usual place :

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

Can reproduce the problem with this version?

Thanks in advance

Gilles Caulier

Comment 4 tuomas.koponen 2023-10-19 12:56:39 UTC

Created attachment 162418 [details]
attachment-356148-0.html

Hi, I think this is now solved. Thanks!

On 19 October 2023 15.46.40 EEST, bugzilla_noreply@kde.org wrote:
>https://bugs.kde.org/show_bug.cgi?id=465652
>
>--- Comment #3 from caulier.gilles@gmail.com ---
>@tuomas.koponen@me.com,
>
>digikam 8.2.0 pre-release have been rebuilt using last Qt 5.15.11 + KDE 5.110
>frameworks. Installer is available at usual place :
>
>https://files.kde.org/digikam/
>
>Can reproduce the problem with this version?
>
>Thanks in advance
>
>Gilles Caulier
>
>-- 
>You are receiving this mail because:
>You reported the bug.
-- Sent from /e/OS Mail.