Bug 126173 - eog cannot display transparent png
eog cannot display transparent png
Product: Fedora
Classification: Fedora
Component: eog (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Depends On:
  Show dependency treegraph
Reported: 2004-06-16 22:41 EDT by Dmitri A. Sergatskov
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-18 18:20:06 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Sample file (transparent png) (6.36 KB, image/png)
2004-06-16 22:43 EDT, Dmitri A. Sergatskov
no flags Details

  None (edit)
Description Dmitri A. Sergatskov 2004-06-16 22:41:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
eog cannot display transparent png images. The background is checkered
black/gray. I cannot verify that image is 100% conformant PNG
(it is created by gnuplot 4.0), but mozilla and "display" (from
ImageMagic) display it correctly.   
I suspect this is fault in one of the libraries since
kview and GQview fail as well. 

Version-Release number of selected component (if applicable):
eog 2.4.0

How reproducible:

Steps to Reproduce:
1.Save the image from URL to the disk
2.open it in eog

Actual Results:  Background is checkered black/gray.

Expected Results:  Transparent background

Additional info:
Comment 1 Dmitri A. Sergatskov 2004-06-16 22:43:29 EDT
Created attachment 101204 [details]
Sample file (transparent png)
Comment 2 Peter van Egdom 2004-06-18 17:16:14 EDT
This is not a bug, but a feature. Both "eog" (and, for example, the
Gimp) use the checkered black/grey background to display the
transparant part of the picture. In "eog" you can use the preferences
screen to specify what to do with the transparant part of the picture.

Note You need to log in before you can comment on or make changes to this bug.