349406 - PNG gets cropped or disappears if it reaches a specific size

Status: RESOLVED WORKSFORME

(Core :: Graphics, defect)

Description

[Manuel Reimer]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.8.0.5) Gecko/20060720 SeaMonkey/1.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20060820 SeaMonkey/1.5a

PNG-Files seem to disappear or get cropped if a specific size is overstepped. This is *bad* if someone tries to create a theme and icons suddenly disappear :-(

The bug seems to be only existent on cairo-gtk2-builds. The file get's displayed without problems on gtk2-builds.

Reproducible: Always

Steps to Reproduce:
You need a cairo-gtk2 build to reproduce this bug. Then try to open the attached PNG file. If the file disappears for you, then you don't see anything. If the file gets cropped, then maybe you don't see the border on the bottom
Actual Results:  
PNG display on cairo builds is broken

Comment 1

[Manuel Reimer]

Attachment: Testcase for the bug

Comment 2

[Robert Kaiser]

The test case works for me in my cairo-gtk2 build but http://prefbar.mozdev.org/messengericons.png (the original image that made this occur for Manuel) fails for me as well.

Comment 3

[Vladimir Vukicevic [:vlad] [:vladv] (needinfo me, slow to respond)]

What version X server?  This is sounding like an X server bug that was in for a while when the source offset of an image wasn't 0.

Comment 4

[Robert Kaiser]

On my side, this is "X.Org version: 6.9.0 - vendor release number: 60900000" according to xdpyinfo.

Comment 5

[Manuel Reimer]

I've now updated to exactly the X-Version used by KaiRo.

Now, after the update, the file still isn't visible if I try to view it in SeaMonkey, but the Theme, using this iconset, now not longer has disappeared icons in Mail/News. Now I at least see the contours. See screenshot.

Comment 6

[Manuel Reimer]

Attachment: Screenshot of Mail/News using the "big PNG file" as iconset.

Comment 7

[Manuel Reimer]

Another, probably important, information:

The SeaMonkey, producing this screenshot, was *not* built with cairo-gtk2. This is a "simple" gtk2 build! So the bug has nothing to do with cairo! Here is my .mozconfig:

ac_add_options --enable-application=suite --enable-toolkit=gtk2
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/manuels_seamonkey_build
mk_add_options MOZ_CO_PROJECT=suite

Comment 8

[Manuel Reimer]

... and the icons which arent "corrupted" in the screenshot are from another file which is smaller as the "messengericons.png"-file which produces most icons in Mail/News.

Sorry for the "comment-spamming", but I need a fix or solution for this problem, as I'm unable to develope the SeaMonkey default theme, if my icons aren't displayed.

Comment 9

[Robert Kaiser]

vlad:
Additionally, I should probably add that my "gtk2" toolkit 1.8 branch build shows all the PNGs correctly, but my "cairo-gtk2" toolkit trunk build shows the error on the image listed in comment #2
Both are self-compiled build with the same compiler and compiler options, running on the same X11R6.9 environment, only differing in building trunk/branch and gtk2/cairo-gtk2.

In combination with Manuel's recent comment, the fault might be some change between branch and trunk...

Comment 10

[Manuel Reimer]

Marking critical, as I think that this bug, at least for SeaMonkey, is a critical problem, as this blocks development of the new Theme.

Comment 11

[Stuart Parmenter]

does this go away if you set MOZ_DISABLE_IMAGE_OPTIMIZE=1 in your environment?  if so, this is a bug in your x server.

Comment 12

[Robert Kaiser]

(In reply to comment #11)
> does this go away if you set MOZ_DISABLE_IMAGE_OPTIMIZE=1 in your environment? 
> if so, this is a bug in your x server.

It does in fact go away with that env var set. This sounds like it is in very current versions of X though, and we (or cairo, I don't know where it happens) should probably work around this for buggy X versions or we'll run into problems on many current systems (I'm seeing this bug in X.org 6.9.0)

Comment 13

[Robert Kaiser]

I'm not seeing this anymore, but I'm on X.org 7.2.0 RC 2 now.

Comment 14

[Matt Woodrow (:mattwoodrow)]

Given that this appeared to have been fixed in X.org 7 (released in 2005), and has had no activity since 2007, I think we can resolve this as fixed.

Please reopen if it's still a problem on current machines.