Bug 15009 - Phototonic settings for exif orientation reversed
Summary: Phototonic settings for exif orientation reversed
Status: RESOLVED DUPLICATE of bug 16347
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Barry Jackson
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2015-01-11 13:51 CET by Barry Jackson
Modified: 2015-08-20 12:38 CEST (History)
1 user (show)

See Also:
Source RPM: phototonic
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Barry Jackson 2015-01-11 13:51:28 CET 
Description of problem:
"Edit -> Preferences -> Viewer Tab -> Rotate image according to Exif orientation" when this box is checked the Exif rotation info is ignored.
When the box is NOT checked the Exif data is used.

Likewise for:
"Edit -> Preferences -> Thumbnails Tab -> Rotate thumbnails according to Exif orientation"

Reported upstream
https://github.com/oferkv/phototonic/issues/170

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Barry Jackson 2015-01-11 14:04:18 CET

CC: (none) => geiger.david68210

Comment 1 Barry Jackson 2015-01-11 14:10:44 CET 
@david
This explains the problem that I was having with image rotation :\
Can you confirm this?
Samuel Verschelde 2015-05-31 22:11:13 CEST

Keywords: (none) => UPSTREAM
Whiteboard: (none) => MGA5TOO

Comment 2 Barry Jackson 2015-06-02 23:55:13 CEST 
Still no more news from upstream on this, I have just pinged them.

It seems that this only affects images from 'some' cameras (e.g. Panasonic) which use the Exif "Rotation" tag.
Comment 3 Barry Jackson 2015-08-20 12:38:22 CEST 
Duplicate of 16347 which states the real cause.

*** This bug has been marked as a duplicate of bug 16347 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE
Note You need to log in before you can comment on or make changes to this bug.