https://bugs.kde.org/show_bug.cgi?id=439135

            Bug ID: 439135
           Summary: color management completely non-functional under
                    Wayland, works under X
           Product: kwin
           Version: 5.22.2
          Platform: Archlinux Packages
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: platform-wayland
          Assignee: kwin-bugs-n...@kde.org
          Reporter: jogir...@zetmail.com
  Target Milestone: ---

SUMMARY

A discussion with a KDE contributor on Reddit revealed that color management is
apparently supposed to be working as of 5.22 under the KWin Wayland compositor.
It mostly works for me in Gnome, but doesn't work at all in KDE.


STEPS TO REPRODUCE
1. Start a Wayland session (startplasma-wayland)
2. Observe whether color corrections previously applied under X are applied
3. Open settings and go to color corrections
4. Try to apply the ICC profile for the screen
5. Try to use colormgr to manually import / apply an ICC profile


OBSERVED RESULT

No color corrections can be applied under KWin. None of the profiles shown
under X show up under Wayland, probably because the device ID is different.
Trying to import any profile (including profiles that were *not* installed
under X) gives the error "color profile is already installed". 

Trying to import a profile with colormgr hangs for a few seconds and then
returns "the profile was not added in time". 

I *can* apply certain test profiles built into colord to the screen, oddly
enough. E.g. there's a profile called Bluish.icc that changes the white point
of the screen to make it much bluer, for testing purposes. I can apply this
profile with colord-kde and it does in fact make my screen much bluer. I was
able to delete this profile with colormgr, and after doing that I can't import
it again (I get the errors described above). So it's possible this issue is
just with *importing* profiles.

Under Gnome, the monitor is correctly detected (although once again without any
profiles because of a differing device ID) and I can import and apply my
profiles, which works as expected. The calibration curves are correctly loaded
in the VCGT under Gnome. Some applications that were previously color managed
under KWin + X are *not* correctly color managed under Gnome. Although the
white balance has been corrected due to the system-wide colord settings, sRGB
images are much too saturated. These applications include Firefox and eog (eye
of gnome). Most applications that allow manually setting a profile (versus
relying on the application communicating with colord) work correctly, e.g.
GIMP.


EXPECTED RESULT

Color management should work as expected. colord-kde should correctly detect my
screen and allow me to apply profiles, and colord should load the calibration
curves into the VCGT when I do so. 

Also, because the Wayland protocol for communicating color management
information between applications and the compositor is not yet finalized or
merged
(https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14),
applications running on a color managed KDE + Wayland system are expected to do
their own color management at this time. Firefox (running under xwayland for
me) should be able to request the active color profile from colord, and send
correctly mapped colors for my screen to the compositor. Same with eog and so
on.


SOFTWARE/OS VERSIONS
Linux: Arch Linux / kernel 5.12.12 / x86_64
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Graphics: Mesa DRI Intel HD Graphics 3000

Please let me know if there's more information I can provide. I'm able to test
stuff and provide additional debugging information as needed.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to