Created attachment 1345367 [details] facebook landing page in both Description of problem: color management negatively affect color rendering in chromium (and chrome) possible starting from version 60 or 61 (was not there in version 59) Version-Release number of selected component (if applicable): chromium-61.0.3163.100-1.fc26.x86_64 How reproducible: always Steps to Reproduce: compare chromium/chrome to firefox while having active color management Actual results: colors differs (seems like double correction is done or something similar) Expected results: have real color as they appear in firefox Additional info: a similar bug was in gimp in the past
Created attachment 1345368 [details] google landing page in both chrome and firefox
Please retest in the Chromium 62 packages I have just pushed as pending updates. It uses gtk3, which may affect the color management. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5b5eb98196
Created attachment 1349849 [details] still broken in 62
Okay. If this is happening consistently in Chrome and Chromium, then the bug lies in the upstream codebase. Please file a bug with Google here: https://crbug.com/wizard Please put a link back to it there, so I can watch it as well.
but it might be fedora specific, because fedora is one of the leading distributions to enable color management. most likely upstream assume no color management and do its own.
> Please file a bug with Google here: > Please put a link back to it there, so I can watch it as well. here is the upstream bug report https://bugs.chromium.org/p/chromium/issues/detail?id=785161
they say it's something wrong with the active color profile I did not changed that, the profile was shipped by fedora
FWIW: I've been looking at various browser color management pages on the web¹ on Vivaldi 13, which is based on Chromium 62, and everything seems fine on my end. I have a WCG monitor with a proper color profile that was generated with DisplayCAL and a colorimeter. In general, using some sort of default color profile defeats the purpose. How likely is it that it'll accidentally match your actual monitor? Might as well use none at all. Actually, that might be what's leading to the color shift you're seeing. Do you even have color management enabled in Firefox? I think you still have to set up the path to the profile in about:config there. If it's off, then that could explain why the colors differ between browsers now. Chromium is managing colors (according to the bogus profile) and Firefox isn't. ¹ Like: http://cameratico.com/tools/web-browser-color-management-test/ or https://webkit.org/blog-files/color-gamut/ or https://translate.google.com/translate?hl=de&sl=de&tl=en&u=https%3A%2F%2Fwww.fotovideotec.de%2Fbrowser_farbmanagement%2Ffarb-testbilder.html Maybe check those websites first in both browsers to get a better idea of what the real problem is.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. 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 '26'. 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 26 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 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 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.