https://bugs.kde.org/show_bug.cgi?id=400712
Bug ID: 400712
Summary: file modification timestamp is updated when images are
moved to collection on removable media
Product: digikam
Version: 6.0.0
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Database-Files
Assignee: digikam-bugs-n...@kde.org
Reporter: lai...@kde.org
Target Milestone: ---
SUMMARY
When moving images from a local collection to a collection on removable media,
the modification time (mtime) of the file is changed to the current time. This
does not happen when moving files within a collection or between two local
collections.
STEPS TO REPRODUCE
1. Create a local collection and a collection on a removable media.
2. Add images to the local collection.
3. Move some images from the local collection to the collection on the
removable media.
OBSERVED RESULT
The timestamp of the moved file is set to the current time.
EXPECTED RESULT
The timestamp should not change when moving files.
SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 5.13.5
KDE Frameworks Version: 5.50.0
Qt Version: 5.11.1
ADDITIONAL INFORMATION
I have observed this behavior with 5.9.0 and actually lost data (images from
old digital cameras without metadata where the mtime was the only hint of the
recording date). Just now, I reproduced it with the 6.0.0-beta2 appimage on a
different machine.
The "update file timestamp when files are modified" option does not seem to
influence the described behavior. Not sure if it is relevant, but I have
configured digikam to only write metadata to sidecar files.
--
You are receiving this mail because:
You are watching all bug changes.
