When nvidia-headless-440 is installed, GNOME has massive graphics problems and wayland is not available on login

[SamuelB.]

# System
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

# Package Versions
nvidia-headless-440 (435, 430)
nvidia-headless-418
nvidia-headless-390

# What you expected to happen
Normal use of GNOME with X11 or Wayland

# What happened instead
Massive graphics problems on GNOME, different "versions" of errors:
- (static) stripes on wallpaper, or evenly distributed artefacts, both can sometimes be erased by changing the wallpaper
- (dynamically) occurring triangles when mouse hovering over menu bar or clicking s.th., basically GNOME is not usable with this
- No wayland option available on login

My xorg.conf looks sane:

Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
EndSection

Section "Screen"
    Identifier "Screen0"
    Device "Device0"
EndSection

Section "Device"
    Identifier "Device0"
    Driver "intel"
    VendorName "Intel Corporation"
    BusID "PCI:0:2:0
EndSection

GPU compute (CUDA. OpenCL) works, I have a Tesla K40.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvidia-headless-440 (not installed)
ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22
Uname: Linux 5.4.0-17-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 1 18:03:57 2020
InstallationDate: Installed on 2017-02-26 (1099 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170226)
SourcePackage: nvidia-graphics-drivers-440
UpgradeStatus: Upgraded to focal on 2019-12-23 (68 days ago)

[SamuelB. (bw-sammy)]

Workaround:
Commenting out a line in /lib/udev/rules.d/61-gdm.rules

#DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"

Found in https://forums.gentoo.org/viewtopic-t-1103246-start-0.html

[Launchpad Janitor (janitor)]

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

[MMason (mmason11)]

I also have this bug with nvidia 150mx.

Workaround worked for me. Thanks.