Created attachment 60411 [details] the limited statistics information of Version 2.0 _without_ faulty pics information Version: 2.0.0 (using KDE 4.6.2) OS: Linux The statistics information ("Statistiken der Datenbank") should contain an additional information: the number and type of unreadable pictures. Why? Assume the number of unreadable pics changes with time- this is a good indicator a harddisk drive maybe loosing realibility. Therefore, one would have time enough to react, as such failures tend to increase with time (or number of boot processes, etc.). I assume, the used components (imagemagick-libraries??) provide such information internally, already. So it would be only an additional step given a professional-like handling feature. Reference: digiKam version 2.0.0-beta5 AVI: 59 GIF: 99 JP2: 14 JPG: 63435 MPEG: 2 NIKON-NEF: 1 PGF: 2 PNG: 874 RAW-CR2: 631 RAW-CRW: 10960 RAW-DNG: 4 RAW-NEF: 31800 TIFF: 879 Gesamtzahl der Einträge: 108760 Alben: 1740 Stichwörter: 46 Datenbanktreiber: QSQLITE Reproducible: Always Actual Results: failed pictures ar _not_ shown, at this time, nor used to offer the user a way to secure his data in time (backup or replacement of harddisk drive) Expected Results: digiKam should check,... 1.) at startup (switch on/switch-off in settings!!!) 2.) whenever one adds pictures to the collection .. if there are faulty/corrupt pics
I think there should be a tool to crawl through the whole archive and check if the images are readable or not. There should be a option to output the list of unreadable pictures. It's always good to know if the images in archive are still sane after for example batch synchronizing of metadata and so could be backed up or opposite if some images needs to be recovered from backup. It would be also good if the tool can not only say - readable / unreadable but check structural sanity of file (like imagmagick utility identify which can diagnose some image corruption).
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.