Bug 401338 - All images lost from albums when connection to network share is lost
Summary: All images lost from albums when connection to network share is lost
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Media (show other bugs)
Version: 5.9.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-23 16:12 UTC by spam-receiver
Modified: 2019-07-14 12:48 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 6.2.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description spam-receiver 2018-11-23 16:12:02 UTC
SUMMARY
Setup of my installation:
* Photos are stores on as NAS server, accessible via a samba share, more precisely a subfolder of the share.
* DigiKam is executed on a Windows PC with access to the share.
* Database backend MySQL is running on the PC (standalone server, not embedded into DigiKam), not the NAS server.
This setup generally works fine. The database is filled with appr. 55,000 photos, all stored remotely.


STEPS TO REPRODUCE
1. Cut the connection (Wifi and LAN) between the PC and the NAS server.
2. The album list as well as all other photo-related views get emptied. 0 (zero) photos left.
3. Restore the connection.
4. All photos have to be read and inserted to the database again.

OBSERVED RESULT
see #2 and #4

EXPECTED RESULT
At #2: This can be acceptable, but a message to the user would be helpful.
At #4: Because scanning 55,000 images over the network takes very long, the database contents should be retained and displayed as soon as the connection is restored. After this, the folders should be scanned for updates, like during the startup of DigiKam.


SOFTWARE/OS VERSIONS
Windows: Win10 (no difference between home and professional version observed)
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2018-11-23 17:49:05 UTC

*** This bug has been marked as a duplicate of bug 377849 ***
Comment 2 Maik Qualmann 2018-11-23 17:52:47 UTC
You can test digiKam-6.0.0-beta3 from here:

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

But make a backup of the databases, because digiKam-6.0.0 makes changes and you may want to go back to the 5.9.0 version.

Maik
Comment 3 caulier.gilles 2019-07-14 12:48:09 UTC
Fixed with #377849 and not reproducible with 6.2.0