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 561162 - EOG Doesn't Open Image With Wrong File Extension (Should Open, Offer Suggestions)
EOG Doesn't Open Image With Wrong File Extension (Should Open, Offer Suggesti...
Status: RESOLVED DUPLICATE of bug 490067
Product: eog
Classification: Core
Component: image viewer
2.24.x
Other Linux
: Normal enhancement
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-17 07:04 UTC by Darin
Modified: 2008-11-17 10:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Darin 2008-11-17 07:04:43 UTC
I discovered this after downloading an image that turned out to be poorly named. Nautilus showed the thumbnail fine, but EOG would not open it. I thought at first the image was corrupt or not downloaded correctly, but that was not the case.

If I try to open a JPEG that is not named with a jpeg file extension, EOG will not open the image. The same with any other image type that is poorly named. I changed the extension on my JPEG and got the following errors:

PNG - Fatal error reading PNG image file: Not a PNG file
GIF - File does not appear to be a GIF file
TIFF - Failed to load TIFF image: Not a TIFF or MDI file, bad magic number 55551 (0xd8ff)
BMP - BMP image has bogus header data

However, other programs I've tried (Mirage, Gthumb, F-Spot, GIMP, Firefox, Midori, Epiphany) opened the image just fine regardless of the bad extension. They even display that the image is in fact a JPEG. Oddly enough, if I simply left the file without an extension, EOG opened it fine!

IrfanView has a great feature in this regard. When opening a poorly named file, it will let you know before displaying the image and ask if you would like the file extension changed to the proper extension. Even though the programs I tried aside from EOG opened the image fine, none suggested the file was badly named or needed correction.

-----------------------------------------------

At the least it would be nice to see the current warning messages also suggest what the file should be.

EOG could also simply open any image file, regardless of naming or extension, just as the other programs do.

A combination of these two would be better. EOG could open the image regardless of extension, and display a warning bar at the top that lets you know that the image is named wrong, and how it should be renamed. Even if it leaves it up to you to find the file and change it.

Ideally, EOG would open the image, with a warning bar at the top of the image suggesting how it should be renamed, and offer to change the file extension for you.

Thanks a lot!

- Darin
Comment 1 Claudio Saavedra 2008-11-17 10:06:31 UTC
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 ***