Description of problem: Fedora's build of Firefox sets the default of gfx.color_management.enablev4 to true; where upstream is set to false. Additionally, Fedora Workstation uses GNOME which in turn uses colord which in turn creates a v4 ICC profile from the display based on EDID chromaticity values. And that sequence is leading to v4 related rendering bugs in Firefox. Version-Release number of selected component (if applicable): firefox-50.0-1.fc25.x86_64 How reproducible: enablev4 true is the Fedora default; it can cause problems because Firefox qcms doesn't strictly support v4, so enabling v4 is probably not a good idea by default because it can cause significant rendering problems. Actual results: See upstream bug report for an example of the bad rendering that can happen as a result of this setting: https://bugzilla.mozilla.org/show_bug.cgi?id=1320588 Expected results: One of two things needs to happen on Fedora, either gfx.color_management.enablev4 needs to match upstream's default (false). Or colord needs to build v2 profiles instead of v4. Additional info:
If gfx.color_management.enablev4 is set to false on Fedora to match upstream, it will mean no display compensation for most Fedora users, because most users get a colord built display profile built to the v4 spec. That would be something of a regression, unless colord is also modified to built v2 display profiles. Obviously the better fix is to figure out why qcms is messing up the rendering when enablev4 is true in the example case, but not every v2 + v4 case.
Richard, disabling v4 sound reasonable for me, because we don't have fix for qcms yet. Do you think we can do anything about it like providing v2 display profile for users who seeks color correction in Firefox?
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.