You are not logged in.
I'm running arch on a Lenovo Carbon 6th gen. Previously I would force the adjustment of colours within chrome or firefox under X to something like sRGB and this would reduce the over saturation of reds/greens/blues. It pretty much then matched my Apple devices. However moving to Wayland I wanted to select a colour profile for the entire desktop environment and not have to tweak browser settings. I've gone through numerous pages trying different icc profiles - none of them change the colour saturation problem - to be honest if I select D65, sRGB, very little actually changes. I'm wondering are there still issues with colour profiles under Wayland or am I missing something?
Originally I installed the icc profile from the link under this article, specifically a calibrated screen similar to mine - I know that might not match my exact screen but it should be closer. This makes no difference to the over saturation.
https://wiki.archlinux.org/title/Lenovo … on_(Gen_6)
I'm aware that Wayland doesn't have a way of installing colour profiles but I've use colormgr to add them and I can then see them in Gnome settings to select and activate them. Selecting and rebooting doesn't make very much of a difference to my over saturation issues.
I was going to try and find my profile from the instructions showing how to unpack the windows inf file (https://support.lenovo.com/pa/en/downloads/ds502150) from here: https://www.thinkwiki.org/wiki/Colour_profile
but when I try and obtain my edid it doesn't return any edid information
sudo modprobe i2c-dev
sudo get-edid | parse-edid
Section "Monitor"
Identifier ""
ModelName ""
VendorName "AUO"
# Monitor Manufactured week 0 of 2017
# EDID version 1.4
# Digital Display
DisplaySize 310 170
Gamma 2.20
Option "DPMS" "false"
Modeline "Mode 0" -hsync -vsync
EndSection
So there's no way for me to map my device information to the icm file that I should be using. I'm not convinced this will drastically change the outcome however.
Under Wayland none of the previous colour options I used within Chrome and Firefox have any affect on the colours as they used to under X.
One oddity my device id from obtaining edid information would have been eDP-1, however adding colour profiles - using color-mgr get-devices, my device is labelled as "xrandr-AU Optronics-0x2036-0x00000000" - does that look correct now I'm using Wayland?
Otherwise I've no idea why changing profiles isn't changing the properties of the screen and why colours still look over saturated to me.
Anything else I can try, or are there still known issues with Wayland and colour?
Thanks for any help
Darren
Offline