Closed Bug 482287 Opened 11 years ago Closed 9 years ago

color photos (graphics) display as black and white 50% of time


(Firefox :: General, defect)

Not set





(Reporter: rufusl2001, Unassigned)


(Whiteboard: [CLOSEME 2011-1-1])

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2

On any/all sites, photos display as black and white 40-50% of the time. And example:

The most obvious problem is where thumbnails display color and actual image displays black/white. Copying link and opening in a different browser displays correctly. FF 3.05 also had this problem after an automatic upgrade late last year or early this year.

Reproducible: Sometimes

Steps to Reproduce:
1.Surf for any site w/photos.
2.Click on photo or thumbnail.
Actual Results:  
Intermittant but continues to happen 2 or 3 times a day.
Go here for another quick example:

20-40% of each group display b/w; copy/paste pic location to another browser and it's color.
OTOH, these groups all render each pic in color...
I second this bug on Ubuntu Jaunty 9.04 with Ubuntuzilla

I figured out this bug only applies to PNG pictures with FF 3.5. Downgrading to 3.0 solved the problem for me.
Reporter, are you still seeing this issue with Firefox 3.6.12 or later in safe mode? If not, please close. These links can help you in your testing.
Also, please consider using the most recent Firefox 4 beta build, your bug may be resolved there.
Whiteboard: [CLOSEME 2011-1-1]
That was a long time ago. I haven't spotted that problem in a while using 9.04+ distros, so you can consider this case closed.
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Ditto Nicolas Bouliane. I have not seen this problem for the last several revisions. 

Looks like it's fixed.
You need to log in before you can comment on or make changes to this bug.