Summary: | Adjust Exif orientation tag - wrong permission interpretation | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Andrzej <superandrzej> |
Component: | Metadata-Orientation | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 0.9.3 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.6.0 | |
Sentry Crash Report: | |||
Attachments: | error message |
Description
Andrzej
2007-11-01 20:23:14 UTC
Still present in digikam 0.9.3 Andrzej, Still reproductible with digiKam 0.9.4 or 0.10.0 using a recent version of Exiv2 library ? Gilles Caulier Created attachment 29207 [details]
error message
Gilles, Yes it is still present. The difference is that error message persist as can be seen in the attachment but orientation tags are changed anyway in all selected files. I also noticed that using "Adjust Time & Date" generates no error message but does not work i.e. the date is not changed although something is being processed. To avoid above problems I have to remount FAT32 partition with current user being owner. But this is not optimal solution. Andrzej Andrzej, I remember that somebody work on a similar problem few time ago. It's only for current implementation from svn (digiKam 1.0.0-beta3 + libkexiv2 from KDE 4.3) Can you take a look ? Gilles Caulier Gilles, I checked. Now doesn't matter whether FAT partition was mounted as root or as normal user. All selected images can have orientation tags changed with no error message but... the interface freezes and I have to kill digikam. :( The last message that I can see is: "Revising Exif Orientatin tags. Please wait ..35%" Do you use current code from svn (1.0.0-beta3) or 1.0.0-beta2 package already released, because i remember a fix from Marcel recently... Gilles Caulier I still use 1.0.0-beta2. Release Plan says that 1.0.0-beta3 should be released within few days. I will compile it and let you know. Andrzej With 1.0.0-beta3 it works as expected. Thank you Andrzej |