YouTube video still visible (hardware chroma key) after reboot on the GRUB screen

[Thomas]

There was a glitch as I was watching a youtube video that imprinted a still image on the screen with transparent vertical stripes. Restarted the computer and the same image was imprinted behind the GRUB boot-loader menu during start up. Unusual behavior that continued 2-3 times after resets including removing all power sources for a while before restarting.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-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.02.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 465.27 Thu Apr 22 23:21:03 UTC 2021
 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1)
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sat Jul 17 23:57:09 2021
DistUpgraded: 2021-05-08 18:27:26,605 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: hirsute
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 465.27, 5.11.0-22-generic, x86_64: installed
 virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1080] [1458:3717]
InstallationDate: Installed on 2021-02-02 (165 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming 5
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to hirsute on 2021-05-08 (70 days ago)
dmi.bios.date: 10/30/2018
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F11
dmi.board.asset.tag: Default string
dmi.board.name: Z370 AORUS Gaming 5-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd10/30/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGaming5-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z370 AORUS Gaming 5
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2
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:1.20.11-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

[Daniel van Vugt (vanvugt)]

Obviously GRUB and YouTube shouldn't be sharing the same screen. That looks like a driver/browser chroma-key bug. What browser were you using?

I'm also not totally confident that's even the main issue you were describing. If it's not then please be sure to open a second bug about the other issue.