[nouveau] Weird colors after startup (Ubuntu 22.04)

[Oliver Tacke]

[Workaround/Fix]

1. When starting the Ubuntu live image, select the option 'Ubuntu (safe graphics)' from the boot menu.

2. During installation be sure to select the third-party software option checkbox in order to get the right Nvidia driver installed.

[Original Description]

I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu appears. When hitting "Try Ubuntu", the screen turns black for a couple of seconds and then re-appears in yellow and brown colors, feels like a 4 color display (white, black, yellow and orange) and I can hardly see anything - sending this bug report from that live system right after starting it up.

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: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:54:05 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Micro-Star International Co., Ltd. MS-7C56
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/username.seed maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.40
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550-A PRO (MS-7C56)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C56
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
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.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

[Damon Howe (en1gma)]

the try ubuntu screen is fine.
after booted to desktop for a split second the screen colors are normal and then BAM i get an almost all white screen
i have tested with 2 systems and 2 video cards.

intel b660 + 12600k nvidia 3060 ti
amd x570 + 5600x nvidia 3060 ti
both systems have same behavior.
i am pretty sure this started happening with the ubuntu 22.04 daily after 03-28-2022 but not 100% sure
i reported it over and over in the #ubuntu #ubuntu-next for 3 weeks and warned everyone repeatably.
i tried to get other people to verify with similar systems and while doing that i got silenced where i couldnt talk and i got kicked out #ubuntu-next.
they told me to report the bug but i first wanted to make sure it was happening on other peoples systems and i was in the process of that very thing when i got silenced.
it is very clear that there are some people there who dont like nvidia.

i would like to add that it is fine while using a nvidia 1060.

thanks

[Oliver Tacke (otacke)]

@Damon Does not sound like a pleasant experience.

The issue is probably related to Wayland and Nvidia drivers then. Doesn't look to good for Ubuntu if prospect users try the live system and one of the first experiences that they make is a corrupted screen.

[Launchpad Janitor (janitor)]

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

[zeli (zeli0726)]

I have the same issue, i boot up the live system from flash drive and when i click 'Try Ubuntu', the screen goes black and when it comes back, my entire screen is red-orange. I attached a picture as reference. If i make a screenshot, it looks fine. I also use dual monitors and the other monitor is so bright it's not even usable.

VGA: RTX 2070 Super
Monitor: LG 27gl83a

[Alejandro R. Mosteo (mosteo)]

Same here, trying the first stable live release of 22.04. I get a weirdly saturated green-lime combo. Picture attached.

VGA: Intel HD Graphics 530
Monitor: HP LE2201w

[Allen Lowe (lallenlowe)]

I'm having the same issue with an RTX 2080. If I start up in safe graphics mode, it works. But of course then I get degraded graphics.

[FM33 (fm33)]

In my case the screen stayed black with a few color spots and it happens only with X.org
By clicking directly on "install ubuntu", I could install and it booted fine. I noticed performance issues and tried X.org session and got the display bug again. While I had selected "Auto logon", I had to use recovery mode to get back on wayland with :
sudo nano /etc/gdm3/custom.conf
and edit WaylandEnable=
There is also a line for auto logon by the way.
Unfortunately, with wayland I'm experiencing frequent freezes and I am falling back to Focal on this machine.
Edit : This is an intel machine (Celeron N3150)

[Daniel van Vugt (vanvugt)]

Oliver,

Please open the 'Additional Drivers' app and use it to install the official Nvidia driver. Then after rebooting does the bug persist?

[Oliver Tacke (otacke)]

@Daniel

I'll gladly do that, but I won't get my hands on that computer before Thursday and I'd need to either figure out how to create a persistent live stick or to install 22.04 on a separate partition or drive.

[Launchpad Janitor (janitor)]

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

[tomeq_ (t-glowacki)]

Same here -
Nvidia 3060 Ti on AMD X570 platform
Panasonic 4K TV via HDMI cable.

While welcome screen is fine - the one with "Install" or "try ubuntu", then the screen blink for a while then return with fluo-green-yellow colorset. It is hard to read anything.

Re-inserting HDMI cable to force reset the link has no effect.

[Daniel van Vugt (vanvugt)]

I don't want to spend too much time on nouveau bugs when it has so many known problems. So all Nvidia owners please open the 'Additional Drivers' app and install the proprietary Nvidia driver from there.

[Daniel van Vugt (vanvugt)]

Has anyone tried logging into a Wayland session to see if that avoids the bug? On the login screen it will either be called 'Ubuntu on Wayland' or just 'Ubuntu' if the only other option is 'Ubuntu on Xorg'.

[tomeq_ (t-glowacki)]

@Daniel - I wish I could but how I can do that, when the screen is totally unreadable (click blindly around especially on 4K display? ;) ) and this is just live USB drive before any installation happening?

[Daniel van Vugt (vanvugt)]

Keep it simple. Please start with only the AMD GPU.

If you have a laptop, just disconnect the external monitor.

If you have a desktop, just move the monitor connection to the motherboard. You might have to also temporarily remove the Nvidia card during that time or else the system will still prefer Nvidia even while no monitor is connected to it.

Once you can use the machine with only AMD graphics, you can install the Nvidia driver manually (even when no Nvidia card is installed):

  sudo apt install nvidia-driver-510

and reboot. Then it should be safe to go back to using Nvidia and multi-monitors.

If you're installing Ubuntu from scratch then the shortcut to all this is to choose the third-party software option during installation.

I am of course guessing that the problem is the nouveau driver and not AMD...

[tomeq_ (t-glowacki)]

@Daniel - I understand how to troubleshoot things and your steps seems very valid, but.... I don't have any discrete AMD card right here to test.

Also - AMD Ryzen CPUs are not equipped with builtin GPU :)

Whole case is about the installation process is simply impossible to be accomplished for 99% of the users. Screen get yellow-green when you click any of the available options in the installer, "live" or "install". That's it.

[zeli (zeli0726)]

I created a live USB stick with persistent store on it to test the workaround, and the system booted up fine. I didn't get screen where you choose between 'Try Ubuntu' or 'Install', so probably that's why it is working. I checked it and the nouveau driver was selected so i'm not sure if it's directly related, something is messing up the screen when you click on the try button.
Also i usually don't use persistent space because it makes the live boot very slow.

[Daniel van Vugt (vanvugt)]

When you first boot the live USB you should probably choose "Ubuntu (safe graphics)" instead of "Try or Install Ubuntu". Despite sounding different they are the same thing with the only difference being that troublesome graphics drivers are disabled in safe graphics mode.

[Oliver Tacke (otacke)]

Hi all!

I've installed Ubuntu 22.04 for real and using the proprietary driver in fact solves the screen issue.

However, in my opinion, someone who wants to try Ubuntu from a live stick should not need to worry about such things (e. g. also try using safe graphics mode). That person is likely to not know much about Ubuntu or maybe even about Linux. If the very first impression is such a problem, then I'd probably look for a different distribution quickly or stick with whatever OS I was using.

[Daniel van Vugt (vanvugt)]

I completely agree, it's a bad user experience.

The reason why proprietary drivers like Nvidia are historically not installed by default I think is because they have their own license conditions.

In practice the real problem here seems to be the bugginess of the open source nouveau driver you will get instead. It's been causing pain for us for years and I would tend to think we should partially disable it. Maybe just disable the acceleration part (mesa) and not the KMS part (kernel).

[Daniel van Vugt (vanvugt)]

This might turn out to be related to bug 1965882.

[jjoonathan (jjoonathan)]

I see this bug with an AMD 5600X + NVidia 3090 + a single display, so you don't need multiple GPUs or a secondary monitor.

[Daniel van Vugt (vanvugt)]

Yes we know. This bug became a single-GPU bug in comment #22.

[Damon Howe (en1gma)]

dont forget i reported this in the main #ubuntu and #ubuntu-next way before the actual final release came out.
i think i reported it for the first time around 03-28-2022.
my nick is en11gma
i reported it at least 4 more times. #ubuntu would just tell me dont talk about 22.04 yet because its not supported offiically yet and goto #ubuntu-next (which i did) and i reported it over and over.
the mods there just wanted to be bullies and go after me because i didnt create a fix it ticket.
i wasnt sure if it was just something i messed up so i didnt want to report it as i was trying to get another person to reproduce it at least. no one would help.
i knew with the final release coming this was going to come out this way but i did try.
now many users wanting to experience 22.04 dont get too. bummers.

[Daniel van Vugt (vanvugt)]

For future reference, launchpad.net is the only officially recognised location for tracking Ubuntu bugs.

[Andrii Litvinov (andrii-litvinov)]

I struggled with this issue for a while until I discovered thar the issue is with the color profile as described in this question https://askubuntu.com/questions/1404516/screen-turns-yellow-even-using-the-live-option-ubuntu-22-04.

The way to solve it for me was to add a new color profile in Setting/Color tab -> Add profile for a display. "Standard Space - sRGB" works just right for my Dell XPS 9560 laptop.

The issue must be with how the default color profiles are generated for a screen. I have an external monitor and there were no issue with colors there.

[Sebastien Bacher (seb128)]

Note that in kinetic we are switching to pipewire, unsure if that has the same issue

[Daniel van Vugt (vanvugt)]

Pipewire isn't involved in putting pixels on the screen.

[Sebastien Bacher (seb128)]

sorry the previous mention to pipewire was for bug #1877194

[Sebastien Bacher (seb128)]

We aren't considering the issue as rls target at this point, it's on a limited set of hardware and the nvidia drivers don't have the issue and can we used instead

[Robert Helewka (heluca)]

Nvidia 3090 on an Alienware R10: boots normally, but the desktop appears as shades of bright green.
It was corrected when I followed Andrii's solution in comment #28.
Thank you Andrii, you just saved me a bunch of time.

I had already tried the Live USB and installed 22.04 on my Gigabyte Aorus X5 MD Laptop (Nvidia 1080ti) and I have not encountered this issue on it.

[jeejah42 (jeejah42)]

> We aren't considering the issue as rls target at this point, it's on a limited set of hardware and the nvidia drivers don't have the issue and can we used instead

This behavior is also occurring on non-nVidia hardware:

$ dmesg |egrep '(CPU|fb|i915)' |grep -v '0x[0-9a-f]*fb[0-9a-f]*'
[ 0.057997] smpboot: Allowing 4 CPUs, 0 hotplug CPUs
[ 0.058224] setup_percpu: NR_CPUS:8192 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1
[ 0.175649] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.218117] rcu: RCU restricting CPUs from NR_CPUS=8192 to nr_cpu_ids=4.
[ 0.239261] CPU0: Thermal monitoring enabled (TM1)
[ 0.239261] MDS: Mitigation: Clear CPU buffers
[ 0.239261] smpboot: CPU0: Intel(R) Pentium(R) CPU N3700 @ 1.60GHz (family: 0x6, model: 0x4c, stepping: 0x3)
[ 0.239261] smp: Bringing up secondary CPUs ...
[ 0.239261] .... node #0, CPUs: #1 #2 #3
[ 0.247844] smp: Brought up 1 node, 4 CPUs
[ 0.413818] pci 0000:00:02.0: BAR 2: assigned to efifb
[ 0.795846] fbcon: Taking over console
[ 0.989716] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.989957] efifb: probing for efifb
[ 0.990013] efifb: showing boot graphics
[ 0.992809] efifb: framebuffer at 0x80000000, using 4128k, total 4128k
[ 0.992823] efifb: mode is 1366x768x32, linelength=5504, pages=1
[ 0.992826] efifb: scrolling: redraw
[ 0.992827] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.998870] fb0: EFI VGA frame buffer device
[ 2.931834] i915 0000:00:02.0: vgaarb: deactivate vga console
[ 3.002852] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0
[ 3.104714] fbcon: i915drmfb (fb0) is primary device
[ 4.548010] i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[ 20.618832] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
$

[jeejah42 (jeejah42)]

> non-nVidia hardware

The above is a Dell Latitude 3160 Pentium-powered Chromebook-class educational laptop. Built-in screen. Problem occurs when booting from USB stick and choosing 'Try Ubuntu' (or 'Try Ubuntu Budgie'), with 22.04.1-LTS (Jammy).

[Daniel van Vugt (vanvugt)]

jeejah42, it sounds like you need to log a separate bug. Please do that by running:

  ubuntu-bug linux

[zemerdon (zemerdon)]

I have this happened to me in the Kubuntu 23.04 Live installer also.

nvidia 3060ti ko.

Safe graphics works as a workaround.

[Ashu (ashusharma)]

I am facing the same issue.
Nividia GTX 1050 Ti. Using Proprietary and tested drivers under Additional drivers.
Asked the question here:
https://askubuntu.com/questions/1467556/ubuntu-22-04-lts-yellowish-screen

[Daniel van Vugt (vanvugt)]

This bug is about the open source nouveau driver only.

The issue in comment #38 is covered in bug 938751.