Hello, I suddenly find a lot of broken photos and videos. The media often can no longer be opened or has large grey or brown areas. I'm currently restoring them using backups. Can digikam recognise broken JPG or mp4 and put them together in a list? Otherwise I'll have to look through all 80,000 files. :-/ Cheers Andy
Hi Andy, In the maintenance tool, existing process to cleanup|repair the database already exists, but not one to identify the broken files. I think we have already a file in bugzilla about this topic. Ideas: - Using the image quality sorter tool to identify the broken files over the collections. A broken file is a image which cannot be open for reading. This can be an intensive task, which can be complex to achieve and not safe to run due to hardware failures. - Using a 3rd-party script to identify broken file on disk. It will be more safe as the digiKam database will be corrupted too. Some pointers: https://stackoverflow.com/questions/46854496/python-script-to-detect-broken-images https://www.davidebarranca.com/2018/05/automated-check-for-corrupted-image-files-with-python-and-imagemagick/ https://codeonby.com/2022/05/07/python-for-data-recovery/ https://aravinda-gn.medium.com/how-to-detect-and-remove-corrupted-image-files-in-an-image-dataset-using-python-3749d8ea5ba8 https://support.microsoft.com/en-us/topic/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e https://www.disktuna.com/finding-out-which-file-is-affected-by-a-bad-sector/ Tips: uses a more robust backup and restore strategy as explained in the online documentation: https://docs.digikam.org/en/asset_management/data_protection.html Best regards Gilles Caulier
See a
See also the related bug 274363
*** Bug 274363 has been marked as a duplicate of this bug. ***
The same is Bug 424441. Maik
Hello and thank you for the links. I'll read through them. Please excuse me if I haven't found it in other bug reports. digikam has crashed a lot in the last few days. Often with a blue screen. Although I closed the program normally, I could still see the program as a background process in the task manager for a long time. I think even several times. With the version from February 17, 2025, it no longer happened. Cheers Andy
*** Bug 424441 has been marked as a duplicate of this bug. ***