Ubuntu
eog package

some PNG files refuse to load

Bug #380975 reported by Dereck Wonnacott on 2009-05-27

This bug report is a duplicate of: Bug #172416: eog determines image type from filename. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	eog (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: eog

Attaching a culprit file or two. They load fine in FF and GIMP.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/eog
Package: eog 2.26.1-0ubuntu1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: eog
Uname: Linux 2.6.28-11-generic i686

Tags:

Revision history for this message

Dereck Wonnacott (dereck) wrote on 2009-05-27:

1237100850.half.drechu_destruction.png Edit (19.5 KiB, image/png)
Dependencies.txt Edit (3.5 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (26.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (767 bytes, text/plain; charset="utf-8")

Revision history for this message

Dereck Wonnacott (dereck) wrote on 2009-05-27:

1237171115.tempt_steampulp.png Edit (182.7 KiB, image/png)

again, loads fine in FF and gimp

Revision history for this message

Steffen Banhardt (steffenbanhardt) wrote on 2009-05-27:

The output of

$ file 1237171115.tempt_steampulp.png
1237171115.tempt_steampulp.png: JPEG image data, JFIF standard 1.02

shows, that the file is a jpg and not a png, renaming it to png makes it possible to open it with eog.

The problem is IMO that eog just says that the file is an invalid png and does not check, what filetype it is.

Revision history for this message

Steffen Banhardt (steffenbanhardt) wrote on 2009-05-27:

TThank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #172416 , so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.