[Digikam-devel] [Bug 138540] New: Pictures files are updated (but not modified) when setting new metadatas albeit they are unset
Fabien
fabien.ubuntu at gmail.com
Fri Dec 8 15:33:46 GMT 2006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=138540
Summary: Pictures files are updated (but not modified) when
setting new metadatas albeit they are unset
Product: digikam
Version: 0.9.0-svn
Platform: Ubuntu Packages
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: Metadata
AssignedTo: digikam-devel kde org
ReportedBy: fabien.ubuntu gmail com
Version: 0.9.0-svn (using KDE KDE 3.5.2)
Installed from: Ubuntu Packages
OS: Linux
When digikam is configured to not save any metadata, it still call exiv2 to write metadata to file.
Note: as expected, it doesn't put new comment, tag, rating into the file, it just rewrite the file, without modifying it.
1) digikam configuration
[Metadata Settings]
IPTC Author=
IPTC Author Title=
IPTC Copyright=
IPTC Credit=
IPTC Source=
Save Date Time=false
Save EXIF Comments=false
Save IPTC Credits=false
Save IPTC Photographer ID=false
Save IPTC Rating=false
Save IPTC Tags=false
2) example
if I modify a comment (or tags, rating) on a picture, its file has a new date. File is still the same (same md5sum).
3) how to check that exiv2 is called for that
I have an album directory with that (note that the directory is not writable):
$ ls -la
total 3079
dr-x------ 2 fabien fabien 112 2006-12-08 16:05 .
drwxr-xr-x 14 fabien fabien 408 2006-12-08 16:06 ..
-rw-r--r-- 1 fabien fabien 1642429 2006-12-08 16:05 img_3402.jpg
-rw-r--r-- 1 fabien fabien 1506637 2006-12-07 19:39 img_3403.jpg
When a change the comment, this is what I have :
digikam: Cannot save metadata using Exiv2 (/localhome/fabien/Pictures/test04/img_3402.jpg: Failed to open file (w+b): Permission denied (13))
Why Exiv2 returns an error although file is read/write ?
Because it first writes a temporary file (if size > 1MB), then remove the old one and rename the created file to the original name.
Why trying to save metadata (digikam is configured to not save metadata to image file) ?
Well, I guess that's the bug :)
This behavior applies to album gui and image editor.
More information about the Digikam-devel
mailing list