Created attachment 193096 [details] Contains all 3 ICC profiles and their JSON/XML formats decoded with iccDEV DESCRIPTION I've been using these color profiles a lot on Windows 11, I made them in ColorControl: https://github.com/Maassoft/ColorControl My current monitor is a KTC M27P6 HDR1400 Mini LED, these profiles use BT.2020 + Gamma ~2.2 and have been set up specifically for 1400 nits. STEPS TO REPRODUCE 1. Download the attached color profiles 2. Select `M27P6.icm` as the color profile in Display Configuration 3. Apply 4. Repeat 2 and 3 for `M27P6 +15.icm` and compare the white clipping 5. If you also have Windows, repeat 2-4 on Windows and compare OBSERVED RESULT On Plasma, applying the profiles with a brightness boost causes noticeable color washing and white colors clip into light non-white colors (think of GitHub's green buttons or even the yellow droplet icon Breeze uses for ICC profiles). EXPECTED RESULT On Windows 11, the brightness boost profiles correctly make the entire screen brighter with essentially no whitening, washing out, or clipping (+15% seems to have it very slightly on light grays which is why I also have +10%). It looks great. I wish it would work that well on Plasma. SOFTWARE/OS VERSIONS Operating System (available in the Info Center app, or by running `kinfo` in a terminal window): CachyOS Linux KDE Plasma Version: 6.6.91 (6.7 Beta 2) KDE Frameworks Version: 6.376 Qt Version: 6.11.1 Kernel Version: 7.0.11-1-cachyos (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Check the attachment for all of the profiles. If any more info is needed I should be able to provide it
Thanks for the bug report. Please run the following command and paste the output into this report. This will give the kwin developers some basic information about your displays: kscreen-doctor -o Also, can you please attach the output of drm_info, after running it in a terminal, to this report? You'll need to pipe the output of drm_info into a file ( drm_info > ~/info.txt) Thanks!
I tested the profiles and afaict this is the same as bug 522301, and should be fixed by the same MR *** This bug has been marked as a duplicate of bug 522301 ***