Open Bug 456017 Opened 16 years ago Updated 2 years ago

Monochrome pink-and white favicons on some sites only

Categories

(Core :: Graphics: ImageLib, defect)

1.8 Branch
x86
Linux
defect

Tracking

()

People

(Reporter: tonymec, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [workaround see comment #5])

Attachments

(1 file)

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1pre) Gecko/20080919000734 SeaMonkey/2.0a1pre

For a few days, favicons on all pages of https://bugzilla.mozilla.org/ as well as on http://software.opensuse.org/ are now displayed in monochrome pink-and-white in Suiterunner. Both Konqueror and Firefox 2.0.0.16pre (I haven't checked Minefield) still display the former in green, black and red, and the latter in orange on white, which makes me think something has gone wrong with my browser rather than with the sites.

See attached screenshot of some of my tabs: notice the pink chameleon (which should be orange) near the left end, and the series of pink-on-white BMO icons in the right part (tab backgrounds are from userChrome.css).
P.S. Favicons on the Location Bar have the same "weird" colouring scheme.
P.P.S. Also in the Bookmarks menu (and submenus) and in the Bookmarks Manager.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b1pre) Gecko/20080918020356 Minefield/3.1b1pre

also has the bug.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: SeaMonkey → Core
QA Contact: general → general
Possibly caused when CMS switched on (bug 418538). The favicon has an ICC profile and, presumably, your computer's setup is incorrect.

Does setting gfx.color_management.mode to 0 'fix' it?

http://kb.mozillazine.org/Gfx.color_management.enabled#Caveats
(In reply to comment #4)
> Possibly caused when CMS switched on (bug 418538). The favicon has an ICC
> profile and, presumably, your computer's setup is incorrect.
> 
> Does setting gfx.color_management.mode to 0 'fix' it?
> 
> http://kb.mozillazine.org/Gfx.color_management.enabled#Caveats

Contrary to what is said in the above-mentioned KB article, gfx.color_management.mode defaults to 2 in my version of SeaMonkey. Setting it to 0 cures the problem, but only after restarting the application.
That's why he told you with the comment that CMS switched on with bug 418538 (is set to 2 by default now).

It seems that you have a wrong color profile enabled on your system.
Component: General → ImageLib
Keywords: access
QA Contact: general → imagelib
(In reply to comment #6)
[...]
> It seems that you have a wrong color profile enabled on your system.

What could I do against that? gfx.color_management.display_profile is at its default, which is the empty string. OTOH, disabling CMS (by setting gfx.color_management.mode back to zero) seems to give correct colors anywhere I look, so apparently I could leave it disabled -- or are there ill effects to be expected from that?
My gfx.color_management.mode is still at zero, with no ill effects AFAICT. I haven't tested recently if the bug is still present if I "Reset" the pref then restart the app, but I suppose that after all this time, it is WONTFIX?
Whiteboard: [workaround see comment #5]
P.S.
Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120426 Firefox/15.0a1 SeaMonkey/2.12a1
ID:20120426003017
Version: Trunk → 1.8 Branch
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.