Bug 399594

Summary:	Collection being thrown away again and again
Product:	[Applications] digikam	Reporter:	Sebas <djsebas>
Component:	Database-Files	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	5.9.0
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:	6.0.0
Sentry Crash Report:

Description Sebas 2018-10-10 08:39:39 UTC

https://forum.kde.org/viewtopic.php?f=255&t=153810

When restarting the SMB (samba) service on the (linux) server, the network share holding the pictures is unavailable for a few seconds. Digikam (on Windows) immediately removes the tree from collection. I have looked through the options/preferences and did not find an option to prevent this behaviour.
The share is added as 'Network Share.'

BUT, even more, several times lately the collection disappeared while SMB (samba) was still running. I don't know why, but this behaviour of collections fully disappearing again and again is highly undesirable. Note the rescan time on 1Gbit/s for 20000 items / 300 GB is 40-60 minutes.

Requesting: Digikam not dropping the collection when unavailable. Instead display a status 'collection unavailable.' Especially when the root folder of a collection is unavailable Digikam should be smart enough to realize this is probably a reachability issue rather than the user moving or removing the full tree, otherwise the user would have also remove or readded the tree in Digikam settings.

Comment 1 Maik Qualmann 2018-10-10 09:31:39 UTC

You can test the digiKam-6.0.0-beta1:

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

Create a backup of your database, digiKam-6.0.0 will slightly change the database if you want to go back to an older version.

Maik

*** This bug has been marked as a duplicate of bug 377849 ***

Comment 2 caulier.gilles 2019-07-14 07:03:39 UTC

See bug #377849