Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18067 - [chromium] Image rendering fails for some websites

Attached to Project: Arch Linux
Opened by Dave Reisner (falconindy) - Friday, 29 January 2010, 22:50 GMT
Last edited by Dan Griffiths (Ghost1227) - Wednesday, 17 February 2010, 17:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Dan Griffiths (Ghost1227)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: The PKGBUILD for this build of Chromium involves 2 flags in the GYP_DEFINES that prevent some webpages from rendering correctly. In particular, the flags "use_system_libpng=1" and "use_system_libjpeg=1" seem to be the culprits. I can honestly say that I don't fully understand the implications of these flags, but building without them does not prevent libjpeg and libpng from being dynamically linked. I'm currently using the chromium-browser-svn package which does not use these defines, and everything works as intended.

This occurs in the extra/chromium build (prior to the libjpng rebuild) and currently in the testing/chromium build.

Steps to reproduce:
1) Find an embedded image attachment on ubuntuforums.org (e.g. [1])
2) Click it.
3) The page turns black rather than showing the full image.

[1] http://ubuntuforums.org/showthread.php?t=1368631 (post #4)
This task depends upon

Closed by  Dan Griffiths (Ghost1227)
Wednesday, 17 February 2010, 17:32 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 5.0.307.9
Comment by Ionut Biru (wonder) - Friday, 29 January 2010, 23:04 GMT
can't replicate on any screenshot on that link on chromium testing x86_64
Comment by Dave Reisner (falconindy) - Friday, 29 January 2010, 23:45 GMT
Here's a screenshot of what happens after clicking on an attached thumbnail

http://omploader.org/vM2UzYw
Comment by Dave Reisner (falconindy) - Saturday, 30 January 2010, 00:46 GMT
Here's expected behavior as built with the chromium-browser-svn package.

http://omploader.org/vM2Uzcw

The PKGBUILD is slightly modified [1] to allow for depot_tools to be checked out in the build process, rather than installing it as a package.

This bug has followed me from Ubuntu when I was using a daily build PPA. It did not occur with the buildbot release on Arch (chromium-browser-bin) before I discovered the libjpeg linking issue and switched to compiling my own packages.

[1] http://dpaste.com/152393/
Comment by Pierre Schmitz (Pierre) - Saturday, 30 January 2010, 01:35 GMT
I cannot reproduce this either. Could you give us a direct link to a png file which does not display correctly?
Comment by Dave Reisner (falconindy) - Saturday, 30 January 2010, 02:47 GMT
I think I might be muffling terms here. If I view the pictures directly without the framework provided by the forum software (e.g. [1]), the images display correctly, without issue. My first instinct was a rendering issue, but I suppose it's not out of the question that this is related to XML, JS, or CSS.

Since I appear to be on my own with this, I've done some testing...

Test 1: Recompile chromium-browser-svn (build 37572) with same GYP_DEFINES flags from testing/chromium. This [2] is the PKGBUILD I've used.
Result: Fail. Screen gets the black overlay instead of showing the image.

Test 2: Recompile testing/chromium without "use_system_libjpeg=1" and "use_system_libpng=1" flags.
Result: Hrmm... compiles fine, but seg faults on every page (aww snap). This [3] is the PKGBUILD I used.

I tried testing/chromium other computers with same results as me. Black overlay persists on an AMD Athlon running 64-bit and a Pentium-M running i686, in addition to my own Intel C2D running 64 bit.

I going to do some further testing to see which of the defines is actually causing the problem, because at this point I'm unconvinced of my own findings.

[1] http://ubuntuforums.org/attachment.php?attachmentid=141935&d=1262296750
[2] http://dpaste.com/152407/
[3] http://dpaste.com/152409/
Comment by Dave Reisner (falconindy) - Saturday, 30 January 2010, 04:48 GMT
Ok, a half dozen recompiles later, I'm able to pin down exactly which define it is. Adding "use_system_libxml=1" to the -svn PKGBUILD results in a fail, removing it from the testing/chromium PKGBUILD results in a win. The only libxml package I have installed is extra/libxml2. Am I (or the PKGBUILD) missing a package? Is this something that needs to be pushed upstream?

Loading...