Bug 1871

Summary: Corrupted images in Firefox
Product: Mageia Reporter: Edward d'Auvergne <true.bugman>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal Keywords: NEEDINFO, UPSTREAM
Version: 1   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: check
Source RPM: CVE:
Status comment:

Description Edward d'Auvergne 2011-06-20 17:24:38 CEST
Description of problem:

In Firefox 4.0.1, some images are corrupted (maybe 30%).  This has been reported in the firefox forums:

http://support.mozilla.com/en-US/questions/824337

A particularly bad example website is facebook.  But it happens on numerous sites, though not all.  Looking through a facebook album with corrupted imaged and the firefox error console open produces:

Warning: Error in parsing value for 'opacity'.  Declaration dropped.
Source File: http://www.facebook.com/photo.php?fbid=10150205577034538&set=a.164766204537.120462.545789537&type=1&pid=7216754&id=545789537
Line: 0

Warning: Error in parsing value for 'filter'.  Declaration dropped.
Source File: http://www.facebook.com/photo.php?fbid=10150205577034538&set=a.164766204537.120462.545789537&type=1&pid=7216754&id=545789537
Line: 0

I don't know if these are related.  This problem also occurs in 'firefox -safe-mode' so is not related to extensions/plugins.


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


How reproducible:

On certain websites (facebook, twitter), 100%.  Others like Google images, there is no corruption.  Trying to find a permanent link to an image with such corruption.


Steps to Reproduce:
1.  Look at facebook.
2.
3.
Comment 1 Edward d'Auvergne 2011-06-20 17:29:27 CEST
Sorry, this is an exact duplicate of https://bugs.mageia.org/show_bug.cgi?id=1705 !  However changing the gfx.color_management.mode value to 0, 1, or 2 does not fix my problem.
Comment 2 Edward d'Auvergne 2011-06-20 17:31:15 CEST
Ok, setting gfx.color_management.mode in about:config to 0 did fix the problem, after a restart of firefox.
Comment 3 Manuel Hiebel 2011-08-26 22:46:37 CEST
Issue still present with Firefox 6 ?

a yes an upstream bug :)

Keywords: (none) => UPSTREAM

Manuel Hiebel 2011-09-02 22:59:17 CEST

Keywords: (none) => NEEDINFO
Whiteboard: (none) => check

Comment 4 Manuel Hiebel 2011-09-17 23:36:33 CEST
no news, so closing

Status: NEW => RESOLVED
Resolution: (none) => OLD