[graphics/krita] libs/ui: Set default display rendering intent to RelativeColorimetric

Git commit 0724c254523e23de224b44f06d05ae8f5dae250a by Dmitry Kazakov.
Committed on 05/08/2026 at 13:52.
Pushed by dkazakov into branch 'master'.

Set default display rendering intent to RelativeColorimetric

When doing rendering with lcms2 there is no
difference between Perceptual and RelativeColorimetric.
But when delegating color management to Wayland,
Perceptual intent causes compositor (KWin) to apply some
weird transformations, making reference white of the surface
offset relative to the rest of the surfaced (due to tonemapping).

Personally, I guess there is a bug in KWin, because Wayland spec
explicitly says that all reference white values of all surfaces should
look the same:

"Compositors should make sure that all content is anchored,
meaning that an input signal level of 'reference_lum' on one
image description and another input signal level of 'reference_lum'
on another image description should produce the same output
level, even though the 'reference_lum' on both image
representations can be different."

CC:[email protected]

M  +2    -2    libs/ui/kis_config.cc

https://invent.kde.org/graphics/krita/-/commit/0724c254523e23de224b44f06d05ae8f5dae250a

diff --git a/libs/ui/kis_config.cc b/libs/ui/kis_config.cc
index 4354b9d4d7f..6b31920841b 100644
--- a/libs/ui/kis_config.cc
+++ b/libs/ui/kis_config.cc
@@ -1050,10 +1050,10 @@ void KisConfig::setPasteFormat(qint32 format)
 
 qint32 KisConfig::monitorRenderIntent(bool defaultValue) const
 {
-    qint32 intent = m_cfg.readEntry("renderIntent", INTENT_PERCEPTUAL);
+    qint32 intent = m_cfg.readEntry("renderIntent", INTENT_RELATIVE_COLORIMETRIC);
     if (intent > 3) intent = 3;
     if (intent < 0) intent = 0;
-    return (defaultValue ? INTENT_PERCEPTUAL : intent);
+    return (defaultValue ? INTENT_RELATIVE_COLORIMETRIC : intent);
 }
 
 void KisConfig::setRenderIntent(qint32 renderIntent) const