[nvidia] Graphics corruption when resuming from suspend

[Ty Young]

Resuming from suspend results in graphical glitches. These glitches, at least on the cover screen(shows date/time) go away when the Hard Drive spins back up. Additional corruption can occur in overview on currently active applications(Such as Chromium).

Description: Ubuntu 16.04 LTS
Release: 16.04

gnome-shell:
  Installed: 3.18.4-0ubuntu3
  Candidate: 3.18.4-0ubuntu3
  Version table:
 *** 3.18.4-0ubuntu3 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.4-0ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Apr 29 15:56:14 2016
DisplayManager: gdm3
InstallationDate: Installed on 2016-04-23 (6 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Ty Young (bluegoliath)]

Attached image of graphical glitches(cover only, same pattern on active applications in Terminal).

[Launchpad Janitor (janitor)]

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

[Ty Young (bluegoliath)]

Seriously, what the actual fuck?

This bug(and others!) was reported 3 goddamn years ago and you people are still resurrecting it by adding useless tags that in no shape or form help the problem getting solved. If you have no interest in actually fixing the issue then mark it as "won't fix" and let it die since there is clearly *NO* intention of EVER fixing it.

Ubuntu is a buggy pile of bovine manure and Canonical and related community members seem to have little to no interest in changing that. I installed Ubuntu 18.04 LTS only to instantly run into a bug where the launcher would appear on the lock screen and being completely functional. How the actual fuck did that not get fixed in the beta?

IIRC I asked for all the bug reports that I made to be closed since -despite being mostly critical- they were never going to be fixed. If no one at canonical or the surrounding community can at least have the decency to try to fix *CRITICAL* bugs in the software in their distro then at least have the decency to not resurrect *YEARS OLD* dead bug reports that will never get fixed. I'm not asking much here.

inb4 "Ubuntu is a community project and relies on community volunteers"

Sorry, you don't get to use that defense after shouting from the rooftops how (metaphorically) big your dicks are compared to the competition. You want to be a big boy OS? Start actually supporting your distro. There is ZERO reason why an LTS distro should have critical -easy-to-run-into bugs 6 months after it's release(looking at you Ubuntu Gnome, but much probably applies to standard Ubuntu). You drop a deuce of a distro release and then drop another 6 months later.

[Daniel van Vugt (vanvugt)]

> IIRC I asked for all the bug reports that I made to be closed

OK we will use bug 1809407 instead.

Aside from anything else, JournalErrors.txt above is showing this bug is from Nvidia driver version 364.19 which doesn't seem to have ever been officially released so is not supported:

  https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-364

But regardless of the driver version, Nvidia is closed source so neither Canonical nor the community have any power to fix it. We can only track its bugs.

[Ty Young (bluegoliath)]

>Aside from anything else, JournalErrors.txt above is showing this bug is from Nvidia driver version 364.19 which doesn't seem to have ever been officially released so is not supported:

It was from the unofficial "official" Ubuntu Nvidia driver PPA. I remember issues with resuming from suspend was a noted problem on Nvidia's website at the time although I don't know if they were referring to this bug specifically.

>But regardless of the driver version, Nvidia is closed source so neither Canonical nor the community have any power to fix it. We can only track its bugs.

Fine. What about the hundred(thousands?) of other critical bugs with open source software that Ubuntu could fix?

Like https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1575426

OR

https://bugs.launchpad.net/ubuntu/xenial/+source/gnome-session/+bug/1575434

Which was marked as "fixed" because it was fixed in a newer Gnome version. Presumably it's still an issue on 16.04. What the actual hell?

[Daniel van Vugt (vanvugt)]

Neither of those bugs are critical or affecting many people at all. So that's why no developers seem to have fixed them for 16.04 yet.

We have several orders of magnitude more bugs than we can possibly hope to fix. But I do understand your frustration -- I made exactly the same complaint to Canonical years before joining Canonical.

As for Gnome Shell bugs, those are especially unlikely to ever get touched because Ubuntu only really started supporting Gnome Shell properly in 17.10 (which is already past end of life). So Gnome Shell bugs will generally be fixed in Ubuntu 18.04 and later. I know Ubuntu-GNOME existed long before that, but it's not a flavor that the main desktop team supports.

[Luca Osvaldo Mastromatteo (lukycrociato)]

I never had this issue until the 19.04 update, I always used the NVIDIA proprietary driver. In Ubuntu 18.10 is working fine, so I suppose is some sort of regression... I'm curious to try this on another distribution.