[nvidia] gnome-shell frequent restart or crash after unlocking screen or resume from sleep

[alperyilmaz]

First, let me provide necessary information about system or packages

System: Ubuntu 18.04.1 LTS
Package version: gnome-shell 3.28.3-0ubuntu0.18.04.2

The problem started 3-4 weeks ago (probably after updating several packages via `apt update; apt upgrade`

After *almost all* screen unlock or resume from sleep events, this is what happens:
* I briefly see the desktop screen (which is security or privacy problem I guess)
* then login screen comes up, asking for the password
* after I put the password there is a wait (5-10 seconds)
* after that there are two possibilities:
    1. there's brief flash in screen and then screen goes black. i can not fire up tty consoles and i have to use SysRq Magic keys to reboot the system
    2. if it does not crash, I login the system, I see the programs/windows but they're unresponsive for 10-30 seconds. after unresponsive time, gnome-shell restarts and only then system starts to function normally. Then apport-bug is started for gnome-shell, I try to send the crash reports.

I'm not sure this is gnome-shell or gdm3 or Xorg problem. But, apport-crash always starts collecting data about gnome-shell, thus I filed report against gnome-shell. I also filed bug report against xorg (https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1797124).

Let me provide additional info that might help;
- I have nvidia drivers installed in system
- gnome-shell produces tons of journal entries (this apport-crash reports are huge, nearly 150 MB and I cannot upload them)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Oct 10 17:10:40 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-06-01 (131 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

1. Please disable your extensions as we find a large number of crashes are caused by gnome-shell extensions. And you have a lot of them:

b'org.gnome.shell' b'enabled-extensions' b"['center-area-horizontal-spacing@<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'transparentnotification@ipaq3870', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'docker_status@gpouilloux', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'freon@UshakovVasilii_Github.yahoo.com', '<email address hidden>', 'timepp@zagortenay333', '<email address hidden>']"

2. Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

[Karsten W. Rohrbach (byteborg)]

Thanks for pointing out uninstalling the shell extensions. I had the same problem and switching off all custom shell extensions helped instantly.

Basically, this also urges an audit of gnome-shell and associated libraries, as this type of crash _could_ be a security issue triggered by extensions (potentially untrusted thris party data/code).