Summary: | "adjust exif orientation tag" does not change the file | ||
---|---|---|---|
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: | 2.6.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.1.0 | |
Sentry Crash Report: | |||
Attachments: | setup rotation metadata configuration panel |
Description
Andrzej
2012-03-01 22:53:02 UTC
Created attachment 69233 [details]
setup rotation metadata configuration panel
I've already played with these settings. When I try to change orientation flag 2 task appears: 1) "updating orientation in database" and this task completes 2) "Revising Exif Orientation tags" and this task holds at 0%. As the effect image is rotated in digiKam database only. Exif orientation flag is not touched. Each intent to rotate image image adds another progress bar with "Revising Exif Orientation tags" Then I try to close digiKam "finishing tasks" message appears and it stays untill I click "cancel" It seems that something is blocking write access to exig tags. About point 2/, i alreday reported this problem to Marcel recently, and he have fixed it in git/master. please take a care to use last beta2 code from repository. Gilles Caulier Gilles, I cloned digiKam repository tonight: git clone git://anongit.kde.org/digikam-software-compilation digikam-sc but the problem with "Revising Exif Orientation tags" and this task holds at 0%. still persist Andrzej Run digiKam from a console and look which messages are printed as trace when you process exif tag revision Gilles Caulier When I try to change exif tags no new messages appear on konsole (digiKam compiled with debugfull and all digikam related entries are enabled in kdebugdialog) Andrzej Should be that problem, fixed in May *** This bug has been marked as a duplicate of bug 295263 *** Fixed with #295263 |