+++ This bug was initially created as a clone of Bug #1027416 +++ Description of problem: The attached BMP file is not properly displayed by eog. I've just noticed shotwell is broken as well. Gimp and ImageMagick display the BMP file properly - therefore the bug must be in some Gnome library. Version-Release number of selected component (if applicable): eog-3.8.2-2.fc19.x86_64 How reproducible: Always. Steps to Reproduce: 1. Download the attached file. 2. Display it in eog or shotwell. Notice how the image is shifted. --- Additional comment from Dimitri Papadopoulos on 2013-11-06 13:56:56 EST --- --- Additional comment from Dimitri Papadopoulos on 2013-11-06 13:57:46 EST --- --- Additional comment from Fedora End Of Life on 2015-01-09 15:29:50 EST --- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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. --- Additional comment from Dimitri Papadopoulos on 2015-01-10 04:38:31 EST --- This bug is still present in Fedora 21. --- Additional comment from Dimitri Papadopoulos on 2015-01-10 04:41:17 EST --- Version-Release number of selected component (if applicable): eog-3.14.3-1.fc21.x86_64 I'm not sure how to change the version of Fedora ssociated to this bug report. I have change my email address meanwhile and this seems enough to lose "ownership". --- Additional comment from Dimitri Papadopoulos on 2015-01-10 04:53:04 EST --- Bug filed upstream: https://bugzilla.gnome.org/show_bug.cgi?id=742689 --- Additional comment from Fedora End Of Life on 2015-02-17 14:06:06 EST --- Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. --- Additional comment from Dimitri Papadopoulos on 2015-02-17 14:42:48 EST --- Please reopen. As I said bug is still there in Fedora 21.
Still there in Fedora 22. Upstream bug does not seem to have been fixed yet: https://bugzilla.gnome.org/show_bug.cgi?id=742689
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.