https://bugs.kde.org/show_bug.cgi?id=505505
--- Comment #4 from MassimoS <[email protected]> --- Maik, the "scan cannot be interrupted" does not work in real world scenarios with thousands of images. The process should manage gracefully the suspend/hibernate, on one side... this is not interrupting the scan per se but it deadlock digiKam for an unknown reason. In any case if digiKam is interrupted during the scan when it restarts it should provide the correct information as well as for incremental scans afterwords. In reality the interrupt initial scan and the restart should be equal to scan 100 folders and then when I re open digiKam I've added another 200 folders under the same root and maybe added some images in the already existing folders. The scan should work correctly and find the new images as well as the new folders, providing the right count and % progress This is how all other applications works and the expected behavior 😊 Hoping this helps. M -----Original Message----- From: Maik Qualmann <[email protected]> Sent: Thursday, 12 June, 2025 11:04 To: Massimo Savazzi <[email protected]> Subject: [digikam] [Bug 505505] 2 errors on Scan after sleep https://bugs.kde.org/show_bug.cgi?id=505505 Maik Qualmann <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #3 from Maik Qualmann <[email protected]> --- The initial scan shouldn't be interrupted. To avoid having to determine the number of items each time and double-scanning a network drive to see how many files are present, the number of items is determined from the database, which quickly leads to 100% even though scanning is still ongoing. I'll consider how to improve this. Maik -- You are receiving this mail because: You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
