Created attachment 1423993 [details] image showing the problem Description of problem: I have several cameras that produce images which at low level are stored in landscape mode but with a flag in the EXIF data telling that they need to be rotated. When displaying such an image as background, using the "Scaled" style, only the top left part of the photo is displayed. The image that gets displayed does have the correct aspect ratio, but only part of the photo is shown. Typical output of the file program for such an image is: dsc00624.jpg: JPEG image data, Exif standard: [TIFF image data, little-endian, direntries=13, description= , manufacturer=SONY, model=SLT-A77V, orientation=lower-left, xresolution=218, yresolution=226, resolutionunit=2, software=SLT-A77V v1.07, datetime=2016:08:20 14:41:12, GPS-Data], baseline, precision 8, 6000x4000, frames 3 Notice that it says "orientation=lower-left" which indicates that the image needs to be rotated (unrotated would be "upper-left") and "6000x4000" which gives the low-level size of the image. Other programs, such as ristretto, display the image correctly (i.e. in portrait mode and uncropped). Also note that other display styles also produce weird results. Version-Release number of selected component (if applicable): xfdesktop-4.12.4-1.fc26.x86_64 (on Fedora 26) xfdesktop-4.12.4-3.fc27.x86_64 (on Fedora 27) How reproducible: 100% Steps to Reproduce: 1.use attached image as background 2. 3. Actual results: Correct apspect ration of image, but cropped to top-left part. Expected results: Full image, scaled to fit the display. Additional info:
Hmmm ... I can reproduce this. In my hands, it looks like the bottom left is cut off. I can only see half fish. However, I think this would need to be solved upstream. Will you be able to file this upstream at bugzilla.xfce.org or would you prefer that I do? If I were to file the bug report, can I use the attached image in the upstream bug report as well?
(In reply to Mukundan Ragavan from comment #1) > Will you be able to file this upstream at bugzilla.xfce.org or would you > prefer that I do? Can you do it? I don't have an account there. (Although I'm sure it's easy to get.) > If I were to file the bug report, can I use the attached image in the > upstream bug report as well? Yes, you can.
(In reply to Sjoerd Mullender from comment #2) > (In reply to Mukundan Ragavan from comment #1) > > Will you be able to file this upstream at bugzilla.xfce.org or would you > > prefer that I do? > > Can you do it? I don't have an account there. (Although I'm sure it's easy > to get.) > I will file and this and link the report here.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '27'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.