[nouveau] massive yellow screen color corruption

[Dan]

using the "try ubuntu" feature, this is what the entire experience looks like (see the 2nd attached image in comment #2).

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470.2
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 5 15:37:32 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU104 [GeForce RTX 2060] [10de:1e89] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd TU104 [GeForce RTX 2060] [1458:402b]
LiveMediaBuild: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
MachineType: To Be Filled By O.E.M. A320M Pro4 R2.0
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/26/2022
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P7.40
dmi.board.name: A320M Pro4 R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.40:bd10/26/2022:br5.17:svnToBeFilledByO.E.M.:pnA320MPro4R2.0:pvrToBeFilledByO.E.M.:rvnASRock:rnA320MPro4R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: A320M Pro4 R2.0
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
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

[Dan (l1nux2023)]

Here a photo of my screen. The screenshot in comment #1 was made using the built-in screenshot feature, I just realized that for some reason it didn't capture the corruption. (the colors are totally fine in BIOS and Windows)

[Dan (l1nux2023)]

The corruption occurs as soon as "try ubuntu" is clicked and seems to be caused by the "automatic" color-profile being applied ("Automatic - C24F390", Samsung monitor C24F390). It can temporarily be fixed by removing the automatic profile and activating "Colorspace sRGB" profile. A permanent patch would be for the "Try Ubuntu" feature to automatically select Colorspace sRGB instead of automatic.

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1969959, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.