Hmm, I am actually testing Gnome 4.40 with archlinux. I think, colormanagement is functional now. I’m not shure for now, I played too much around with xiccd, dispwin, etc.
Applying ICC profiles to the display/desktop in Settings>Color in Gnome 40.4.0 running on Wayland seems to do something at least. Not sure what else I can do to test, but I’m able to get a fairly noticeable color shift when switching between different profiles on both of my displays.
In Gnome Wayland I am creating a colormanaged CUPS Printserver for dye-sublimation desktop printers.
Gnome version is 3.38 and installed on a Raspberry Pi 4. Debian 32-bit.
After almost endless research it is working as it should be now.
As I understand it wouldn’t be a good idea to update to Gnome 4.0. Is this still a current situation in 2022 july. Does anyone know if the issue is solved?
I’m on Manjaro. with Gnome 42.3 on X11. I don’t really know that much about color managenent, but here are a couple of screenshots comparing my imageviewer (gThumb) and firefox up against darktable. To my untrained eye they look similar to me. Allthough, I do have crappy monitors as well
AFAIK there is no 10-bit color solution in Wayland.
For me, Xfce with Xorg AND a suitable graphicscard AND Nvidia Driver (nouveau doesn’t do as well) AND a modified /etc/X11/xorg.conf.d/30-screensetup.conf, is the only working setup yet.
Arch/64 on Intel PC. Again, it’s not easy on linux (Windows as well).
There’s no 10 bit-color on Rapsberry, I guess. Therefore, it’s always 8 bit and SRGB and Gnome 4 should work.
I just installed Manjaro with Gnome and color management does indeed seem to be completely broken. I run Gnome on x11. When I try to install my screen profile that I created on Debian everything turns reddish. When I try to profile the screen the result is really odd, something like 95% sRGB, 70% AdobeRGB etc. even though I have a wide gamut screen. When I go back to Debian/spectrwm I get 99% AdobeRGB, 160% sRGB.
Uh oh, spectrwm is hardcore. As in openbox, there should be no influences on colormanagement.
Nowadays, all stuff is driven by colord/xiccd (systemd), why is this weird on gnome?
Do you have Nvidiadrivers and an Xorg.conf as I described above?
I know it’s a long time, and maybe the topic is dead, but I managed to calibrate my monitor in Linux, although it was not easy and, honestly, the situation is quite sad.
DisplayCal works, but (at least if you have a SpyderX like me — you know, black Friday) it works only if you have exactly version 2.3.0 of ArgyllCMS, because previous and newer versions have a bug Error – ‘Instrument Access Failed' for LCD White LED Mode | DisplayCAL. Fortunately, the FlatPack version has the correct one
It’s not immediate, but you have to choose the following options:
…and then follow the instructions. I managed to calibrate my old LG IPS display very near to my new BenQ (which come with a ΔE<3 certificate), so I’m happy now.
When importing the ICC profile, you have to convince Gnome to see it (restarting GNOME shell or something like that, I am not sure).
But the situation is not really a happy one. I was almost thinking of calibrating the monitor connecting it to a Windows machine and then exporting the ICC…
I gave up using Gnome anymore. Unusable. Gnome3 guaranteed correct color management.
Using xfce is fine. Actual versions don’t need to play with atom, etc., just use it.
Some developes are bad and messy. KDE3 was perfect. Since 4/Plasma is messy and partly broken yet. Also Gnome4 or 5 or whatever.
Wow, this explains why my colors are messed up since upgrading from ubuntu 20.04 to 22.04…
I even calibrated my screen with the latest version of DisplayCal based on python3 and a Spyder 5 since upgrading ubuntu 22.04.
So according to @Romano_Giannetti the key is getting a valid icc profile out of DisplayCal?
But it seems that the used version of Argyll CMS (2.1.2) is an issue, although I didn’t encounter any error during the calibration process. I however will try to reproduce what @Romano_Giannetti suggested tomorrow.
Sorry for the stupid question, but should “Interactive display adjustment” be turned on or off now?
Using darktable-cmstest I always get an empty output:
XWAYLAND1 the X atom and colord returned the same profile
X atom: _ICC_PROFILE (0 bytes)
description: (none)
colord: "(none)"
description: (file not found)
Only when I go back to DisplayCal to install the profile for all users, darktable-cmstest is able to discover the profile:
XWAYLAND1 the X atom and colord returned different profiles
X atom: _ICC_PROFILE (968540 bytes)
description: DELL U2410 2023-01-14 S XYZLUT+MTX
colord: "(none)"
description: (file not found)
Is there also a general problem with wayland? Did anybody get it working with wayland, or do I have to switch back to xorg?
I had to leave that unchecked. If you check that, DisplayCal tries to guide you to change the color setup of the monitor, and for me it ended with a very greenish thing that was impossible to calibrate. But probably it was my fault — I really struggled to find/understand the information.
By going back in this discussion I learned that wayland does not (yet) support color management and this was exactly my problem. Once I switched back to xorg color management seem to work again.