SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** While converting a hard drive from ext4 to btrfs a corrupt file with a checksum error appeared. When attempting to run Tools/Maintenance/Fingerprints Digikam would crash as soon as the flash screen disappeared. Removing the corrupted file fixed the problem. STEPS TO REPRODUCE 1. Start Digikam which previously was set to Maintenance/Fingerprints 2. Crash 3. OBSERVED RESULT Digikam would not start EXPECTED RESULT Digikam would run SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 20.04.5 LTS Gnome 3.36.8 (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Since the file was corrupted on the hard drive and the copy may not have the potential holes in the file that that entrails it may not cause a crash. Jan 25 06:31:12 LAP2 kernel: [135148.708159] BTRFS warning (device sdc1): csum failed root 5 ino 33752354 off 0 csum 0xecabaf9c expected csum 0xf753f82d mirror 1 Jan 25 06:31:12 LAP2 kernel: [135148.708174] BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 31, gen 0 Jan 25 06:31:12 LAP2 appimagekit_2a4e04dc471bb01ec58428284d627d08-org.kde.digikam.desktop[62310]: #033[34mDigikam::MetaEngine::Private::printExiv2ExceptionError#033[0m: Cannot load metadata from file with Exiv2 backend: /media/pbk/PICT_5TB/2011/08/14/IM000842.JPG (Error # 59 : "corrupted image metadata" Jan 25 06:31:12 LAP2 kernel: [135148.795566] BTRFS warning (device sdc1): csum failed root 5 ino 33752354 off 0 csum 0xecabaf9c expected csum 0xf753f82d mirror 1 Jan 25 06:31:12 LAP2 kernel: [135148.795572] BTRFS error (device sdc1): bdev /dev/sdc1 errs: wr 0, rd 0, flush 0, corrupt 32, gen 0
Where is crash exactly ? Run digiKam into gdb and get a backtrace as explained here : https://www.digikam.org/contribute/ Please also share the corrupted file using cloud to try to reproduce here. Gilles Caulier
Without the GDB backtrace or the presumably causative file "/media/pbk/PICT_5TB/2011/08/14/IM000842.JPG " we can't help. Maik
@kellnerp@earthlink.net digiKam 8.0.0 is released. This file still valid ? Gilles Caulier
@kellnerp@earthlink.net, What's about this file using current 8.2.0 AppImage Linux bundle ? It's reproducible ? https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
@kellnerp, digiKam 8.3.0 stable version is released and available at usual place : https://www.digikam.org/download/ Can you reproduce the dysfunction on your computer ? Thanks in advance Gilles Caulier
Hi, digiKam 8.5.0. is out with many fixes and improvements. https://www.digikam.org/news/2024-11-16-8.5.0_release_announcement/ This report still valid with this version? Thanks in advance Gilles Caulier
Hi, digiKam 8.6.0 is just released: https://www.digikam.org/news/2025-03-15-8.6.0_release_announcement/ Problem still exists with this version? Thanks in advance Gilles Caulier
kellnerp, any feedback here ?