Bug 510791

Summary: Library scan stuck with JPG files
Product: [Applications] digikam Reporter: Breisgauer <richter_joerg>
Component: Database-ScanAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.8.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 9.0.0
Sentry Crash Report:

Description Breisgauer 2025-10-19 15:06:53 UTC 
***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY

During import of new libraries or when starting digikam, SCAN stucks with some jpg files.
the jpg files causing the issue can be previewed in other foto apps like synology photo manager or windows photos or paint.net
opening such files in paint.net and just doing a save fixes the issue .... these photos can be important then.

STEPS TO REPRODUCE
1. import a new collection of photos
2. while scanning the new collection digikam scan stucks
3. closing digikam leaves a digikam.exe process active in task manager ... needs to manually killed

OBSERVED RESULT
scan stucks

EXPECTED RESULT
importing the jpg pictures or ignoring jpg pictures if there is an issue with the photo

SOFTWARE/OS VERSIONS
Windows: windows 11
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: latestes from digikam 8.8

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2025-10-19 15:19:48 UTC 
Can you share using a cloud webservice the JPEG file for analysis ?
Comment 2 Breisgauer 2025-10-19 19:23:05 UTC 
link to share with examples send via private note
Comment 3 Maik Qualmann 2025-10-20 11:19:45 UTC 
We can't reproduce any problem with the two sample JPG files on either Linux or Windows.
If you can actually reproduce the problem, it would be helpful if you could create a DebugView log, as described here:

https://www.digikam.org/contribute/#windows-host

Maik
Comment 4 Breisgauer 2025-10-20 20:39:31 UTC 
(In reply to Maik Qualmann from comment #3)
> We can't reproduce any problem with the two sample JPG files on either Linux
> or Windows.
> If you can actually reproduce the problem, it would be helpful if you could
> create a DebugView log, as described here:
> 
> https://www.digikam.org/contribute/#windows-host
> 
> Maik

DebugView log can be found in the same share where you found the exemplary pictures.
With log item #584 digikam stops scaning. 
I aborted the scan process, and ended digikam. the remaining task for digikam.exe I had to terminate in the task manager
Comment 5 Maik Qualmann 2025-10-21 06:20:13 UTC 
Thanks for the log, the problem is clear. Due to an Exiv2 exception in the image caused by Google's GCamera metadata, digiKam is trying to read the metadata with ExifTool. This isn't a problem; the issue with the GCamera URI is known and intended.
However, ExifTool now hangs. The cause is that you're using an outdated/unsupported ExifTool in a directory you configured yourself (.../OneDrive/Downloads/exiftool-12.89_64/exiftool.exe).
Go to the digiKam setup under Metadata ExifTool and reconfigure the ExifTool in the digiKam directory.

Maik
Comment 6 Breisgauer 2025-10-22 21:11:33 UTC 
Thanks team. You found the root cause. I changed the configuration to use the exiftool which comes with digikam. Works like a charm now. Many thanks for helping me out here!