After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 588505 - Error interpreting JPEG image file (Not JPEG file: starts with 0x89 0x50)
Error interpreting JPEG image file (Not JPEG file: starts with 0x89 0x50)
Status: RESOLVED DUPLICATE of bug 490067
Product: eog
Classification: Core
Component: image viewer
2.26.x
Other All
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-07-14 04:18 UTC by Peter Shinners
Modified: 2009-07-14 13:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Description Peter Shinners 2009-07-14 04:18:35 UTC 
Please describe the problem:
EOG mistakenly cannot load this jpeg image. It loads correctly in Firefox 3.5 and Gimp 2.6. I am guessing the image can load fine, but EOG is falsely detecting an image it cannot load. 

When loading this image in EOG a banner appears in the top with the message shown in the subject.

I am pretty certain that these images used to load correctly in EOG, but I cannot be sure.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?
Yes

Other information:
Comment 1 Peter Shinners 2009-07-14 04:26:52 UTC 
Was unable to attach the image, as it is larger than 1MB. I've uploaded it to my web host, where it should remain available for the medium term future.
http://shinners.org/eog_588505.jpg
Comment 2 Peter Shinners 2009-07-14 04:33:26 UTC 
I just built 2.27.3 and am seeing the same problem.
Comment 3 Felix Riemann 2009-07-14 13:18:16 UTC 
This is actually in instance of bug 490067. If look at the file in detail it will reveal that it is actually not a JPG but a PNG instead (look at Firefox's title bar when you look at the image). The problem is that eog currently relies on the file extension.

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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