Version: 2.6.0 (using KDE 4.8.0) OS: Linux I cloned today git repository. When I use "adjust exif orientation tag" it does not change the file's exif data. Only digiKam database is changed. In digiKam image is displayed OK but in other viewer orientation is not changed. In digiKam 2.4.1 works as expected. Reproducible: Always Steps to Reproduce: Change image orientation using "adjust exif orientation tag" and view in e.g. Gwenview Actual Results: Image's orientation displayed in other viewer is not changed Expected Results: Image's orientation displayed in other viewer is changed OS: Linux (i686) release 3.0.4 Compiler: gcc
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