Bug 514868 - Moving chrome-based windows from laptop to 4K screen changes the app-colors
Summary: Moving chrome-based windows from laptop to 4K screen changes the app-colors
Status: RESOLVED UPSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: colour-management (other bugs)
Version First Reported In: 6.5.5
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 514928 (view as bug list)
Depends on:
Blocks:
 
Reported: 2026-01-20 16:01 UTC by slartibart70
Modified: 2026-01-22 13:04 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
ok (115.06 KB, image/png)
2026-01-20 16:03 UTC, slartibart70
Details
washed-out (55.36 KB, image/png)
2026-01-20 16:03 UTC, slartibart70
Details

Note You need to log in before you can comment on or make changes to this bug.
Description slartibart70 2026-01-20 16:01:58 UTC
Hi,
i have a Laptop screen and a 4K screen.
if i start google-chrome on the laptop screen, all colors are ok (the app is usable).
Same if i start chrome on 4K screen.

The problem starts, when chrome is started on laptop-screen and then moved to the 4k screen.
All colors are then 'washed out' - the app is still usable though. See attachments

This only happens with google-chrome, chromium and brave. Firefox and other app-windows behave properly when moving.
google-chrome: Version 144.0.7559.59 (Official Build) (64-bit)
brave: Brave 1.86.139 (Official Build) (64-bit), Chromium: 144.0.7559.59
Comment 1 slartibart70 2026-01-20 16:02:14 UTC
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.6-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics
Memory: 64 GiB of RAM (58,5 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
Manufacturer: LENOVO
Product Name: 21K5000JGE
System Version: ThinkPad P14s Gen 4
Comment 2 slartibart70 2026-01-20 16:03:12 UTC
Created attachment 188717 [details]
ok
Comment 3 slartibart70 2026-01-20 16:03:39 UTC
Created attachment 188718 [details]
washed-out
Comment 4 David Redondo 2026-01-21 13:58:39 UTC
Most likely chrome issue if it doesnt happen to other applications , but lets see what xaver says
Comment 5 slartibart70 2026-01-21 14:05:11 UTC
yes, pretty sure about this:
especially if we take edge into account - this one wasn't yet updated:
Version 143.0.3650.139 (Official build) (64-bit)

Moving over screen-edges does no harm to edge, all colors stay the same

Beginning with version 144 the problems seem to start
Comment 6 Zamundaaa 2026-01-21 14:42:33 UTC
Definitely a Chrome issue, please report it to Chrome/chromium
Comment 7 slartibart70 2026-01-21 16:08:28 UTC
there is already a bug open in chromium tracker:

https://issues.chromium.org/issues/477318785

Workaround for now:
call chrome with '--disable-features=WaylandWpColorManagerV1'
Comment 8 Zamundaaa 2026-01-22 13:04:26 UTC
*** Bug 514928 has been marked as a duplicate of this bug. ***