Grey (gray) appears as pink in Ubuntu 22.04

[vadim]

Grey (gray) appears as pink in Ubuntu 22.04

WORKAROUND:

Settings > Colour > YOUR MONITOR = OFF

ORIGINAL DESCRIPTION:

i have GPU: NVIDIA GeForce MX150, instead of the usual gray color, my monitor started showing a gray-pink color. I can't take a screenshot because it will just be gray on your monitor (i checked the screenshot in windows 11). Did the developers break something in the video card driver or why did it happen?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CompositorRunning: None
Date: Sat Apr 23 19:54:00 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Xiaomi UHD Graphics 620 [1d72:1701]
   Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701]
InstallationDate: Installed on 2022-04-23 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Timi TM1701
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=907bba42-0e12-469a-9f3b-62991b70869f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/02/2018
dmi.bios.release: 106.121
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: XMAKB5R0P0603
dmi.board.asset.tag: Any
dmi.board.name: TM1701
dmi.board.vendor: Timi
dmi.board.version: MP
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Timi
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 0.3
dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku:
dmi.product.family: Timibook
dmi.product.name: TM1701
dmi.sys.vendor: Timi
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

[vadim (vadim1337)]

i don't really know for sure if this is an xorg problem, but it was fine in the previous version of ubuntu

[Wu (wu)]

Delete the display color profile or choose a proper one solves the problem for me.

[Daniel van Vugt (vanvugt)]

Sounds like bug 938751. Please try:

  Settings > Colour > YOUR MONITOR = OFF

and then restart any affected apps. Or is the shell also affected?

[Daniel van Vugt (vanvugt)]

Please try:

1. Update the system:

   sudo apt update
   sudo apt full-upgrade

2. Reboot.

3. On the login screen select 'Ubuntu on Wayland'.

4. Does the bug still occur in the Wayland session?

5. While in the Wayland session please run:

   journalctl -b0 > journal.txt

6. Attach the resulting text file here.

[vadim (vadim1337)]

1)Ubuntu 22.04 removed Wayland 2)if i set it to sRGB then everything is fine, if it detects the color automatically for my laptop then gray-pink colors appear instead of gray

[Daniel van Vugt (vanvugt)]

Wayland is back thanks to updates last night (bug 1968929).

But this bug sounds like a problem with the default colour profile.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Sebastien Bacher (seb128)]

There is a similar report on https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/610 which got closed as not being a bug but it might be worth adding your input there or report a new issue on gitlab

[vadim (vadim1337)]

i created new issue on gitlab
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/685

[Sebastien Bacher (seb128)]

thanks!

[Steven Clarkson (sclarkson)]

This is the GNOME issue tracking this upstream.

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4071

It was introduced into GNOME 40 by this commit.

https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/e90a75fd59ac41aa331f53492a84712e43bcbce2

There was an attempt to revert it here, that was eventually abandoned as the color transform matrix code was moved to mutter.

https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests/293

I think Ubuntu should patch out this change. Monitors with unreliable EDID, of which there are many, end up with distorted colors. Potentially, monitors with good EDID may have slightly reduced color accuracy, but only to the threshold of GNOME pre-40. Someone for whom that matters is likely manually calibrating their color already.

[Daniel van Vugt (vanvugt)]

That issue was being tracked in bug 1943558 too...

I don't think any patching is necessary here. The very low rate of reports of this issue, and the simplicity of the workaround, indicate that we don't need to prioritise this bug.

[Nathan Bryant (nbryant42)]

The color distortion resulting from this change is very glaring; not even close to accurate color. So either this change should be fixed, reverted, or color management should be disabled by default. All of these solutions are simple; the broken attempt at color management is not.

[Daniel van Vugt (vanvugt)]

It's not that simple because developers are not seeing the bug and so can't test solutions. It's also not common enough that users are reporting it very often either.

Ubuntu 22.10 has now been released with the relevant code rewritten and also moved between projects. So once people agree it's fixed in 22.10, and there's sufficient demand to get a fix in earlier releases then we can consider who might be willing to do and to test patches/reverts.

[Cristi (cristip201)]

Had exact same issue and here is how I solve it:

I've deleted the default color profile and selected the "Best RGB" and the problem was solved. I'm not a designer so I don't know which color profile should be appropriate but "Best RGB" looks good.

[Steven Clarkson (sclarkson)]

This is the patch that I applied to 42.1-1ubuntu2.1 to fix this on our systems.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "revert-system-color-transform-matrix.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Daniel van Vugt (vanvugt)]

Thanks Steven.

I would normally recommend proposing changes upstream (https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/merge_requests) but in this case the functionality moved from the gnome-settings-daemon project into mutter in 43.0. So upstream may not be interested in discussing reverts for 42.x

Perhaps if more people find it useful then we should Ubuntu-patch comment #17 for 22.04 only.

P.S. Does anyone see similar bugs in 22.10 and later?