https://bugs.kde.org/show_bug.cgi?id=511159
Bug ID: 511159
Summary: Rejecting or ignoring faces writes to image metadata,
causing unwanted file modifications
Classification: Applications
Product: digikam
Version First 8.8.0
Reported In:
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: minor
Priority: NOR
Component: Faces-Workflow
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Rejecting or ignoring detected faces in Digikam updates the original image
files’ metadata instead of only changing the database, causing unnecessary file
modifications.
STEPS TO REPRODUCE
1. Run face detection on a set of images.
2. In the People view, reject or mark some detected faces as "ignored."
3. Observe that the image file's last modified timestamp changes.
OBSERVED RESULT
Each time a face is rejected or ignored, Digikam modifies the image file itself
(metadata changes). This happens even though no new face tags or user-visible
metadata should be added or removed.
EXPECTED RESULT
Rejecting or ignoring a face should only affect Digikam’s internal database.
The original image files should remain untouched, preserving their timestamps
and avoiding unnecessary metadata writes.
SOFTWARE/OS VERSIONS
Windows: Windows 11 25H2
Digikam 8.8.0 Stable
ADDITIONAL INFORMATION
This behavior causes significant overhead when images are stored on a NAS or
network drive, since marking many faces as ignored triggers many metadata write
operations over the network.
The modification date changing confirms that Digikam is writing to the files
even when it shouldn’t.
Ideally, “ignored” or “rejected” status should be stored exclusively in
Digikam’s internal database.
I believe this behavior already happened in the past, was fixed, and reappeared
sometime around the 8.7.0 release.
--
You are receiving this mail because:
You are watching all bug changes.
