Created attachment 185757 [details] Washed out colors only on Chromium based browsers SUMMARY Hello, this issue started happening around one week ago after Chromium merged HDR support for Wayland, for me and many other people now the colors on Chromium based browsers look completely washed out, and the only workaround for now is to disable hardware acceleration in the settings or add this argument "–disable-features=WaylandWpColorManagerV1 --force-color-profile=sRGB" I've attached a screenshot of how the colors look now. Here are some links of people experiencing this issue, and the only thing in common between these people is that they are using KDE Plasma: https://www.reddit.com/r/kde/comments/1nzy72u/has_anyone_else_encountered_this_problem_too/ https://community.brave.app/t/washed-out-colors-when-hardware-acceleration-is-enabled/643668 So then I got suspicious and I've tried to see if the issue was present on other Wayland desktops, and I can confirm that on both COSMIC and GNOME I don't have this issue, and the colors look normal even with hardware acceleration enabled. The interesting thing is, that I don't have any HDR capable monitors, so I'm wondering if Chromium is thinking that my monitor is HDR and it tries to display HDR colors, but fails because my monitor is not HDR or there is something else going on, another option I am thinking is that maybe Plasma is giving the wrong information to Chromium about my monitors and that's why it thinks they're HDR capable when they're not? Idk. The other interesting thing is that this is not GPU vendor related, people seem to have this issue with all brands of GPUs, and only on KDE Plasma. STEPS TO REPRODUCE 1. Use a Chromium based browser with Hardware acceleration enabled. OBSERVED RESULT Colors are washed out. EXPECTED RESULT Colors are not washed out. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 42 KDE Plasma KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 ADDITIONAL INFORMATION This issue happens both with native packages and with flatpaks.
chrome bug *** This bug has been marked as a duplicate of bug 509664 ***