X11 session crashes when locked/unlocked

[hamid]

When locking my gnome session either manually (SUPER+L) or via timeout due to inactivity, resuming the session will cause it to crash.

The log shows the following:

Sep 14 20:48:14 freyja systemd[1234]: Reached target Default.
Sep 14 20:48:14 freyja systemd[1234]: Startup finished in 17ms.
Sep 14 20:48:14 freyja systemd[1]: Started User Manager for UID 121.
Sep 14 20:48:14 freyja systemd[1234]: Started D-Bus User Message Bus.
Sep 14 20:48:14 freyja dbus-daemon[1242]: Activating service name='org.gnome.ScreenSaver'
Sep 14 20:48:14 freyja org.gnome.ScreenSaver[1242]: Unable to init server: Could not connect: Connection refused
Sep 14 20:48:14 freyja gnome-screensav[1252]: Cannot open display:
Sep 14 20:48:14 freyja dbus-daemon[1242]: Activated service 'org.gnome.ScreenSaver' failed: Process org.gnome.ScreenSaver exited with status 1
Sep 14 20:48:14 freyja gnome-session[1244]: gnome-session-binary[1244]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
Sep 14 20:48:14 freyja gnome-session-binary[1244]: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
Sep 14 20:48:14 freyja gnome-shell[1254]: Can't initialize KMS backend: could not find drm kms device
Sep 14 20:48:14 freyja gnome-session[1244]: gnome-session-binary[1244]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Sep 14 20:48:14 freyja gnome-session-binary[1244]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
Sep 14 20:48:14 freyja gnome-session-binary[1244]: Unrecoverable failure in required component org.gnome.Shell.desktop
Sep 14 20:48:14 freyja gdm-launch-environment][1224]: pam_unix(gdm-launch-environment:session): session closed for user gdm
Sep 14 20:48:14 freyja gdm3[1198]: GdmDisplay: display lasted 0.276059 seconds
Sep 14 20:48:14 freyja systemd-logind[1106]: Removed session c1.
Sep 14 20:48:14 freyja gdm3[1198]: Child process -1240 was already dead.
Sep 14 20:48:14 freyja gdm3[1198]: Child process 1224 was already dead.
Sep 14 20:48:14 freyja gdm3[1198]: Unable to kill session worker process
Sep 14 20:48:14 freyja systemd[1]: Stopping User Manager for UID 121...
Sep 14 20:48:14 freyja systemd[1234]: Stopping D-Bus User Message Bus...
Sep 14 20:48:14 freyja systemd[1234]: Stopped target Default.
Sep 14 20:48:14 freyja systemd[1]: Received SIGRTMIN+21 from PID 379 (plymouthd).

Nvidia driver version: 384.66-0ubuntu1
Nvidia KMS modesetting according to this bug (https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1697882) is "N" (disabled).

release: Ubuntu Artful Aardvark (development branch) 17.10
kernel: 4.13.0-041300-generic #201709031731 SMP Sun Sep 3 21:33:09 UTC 2017 x86_64
GDM: 3.26.0-1ubuntu1

What happens:

* Open some windows, browsers, terminals etc
* I lock the screen with SUPER+L
* I briefly see my lock-screen wallpaper before the screen goes to sleep
* Screen goes black
* I wake the machine (with space bar)
* I see white lock screen clock on white-background
* Swipe up and see login screen, I login
* Window scaling has reset and all previously opened windows are gone

What I expect to happen:
* lock screen and see lock-screen wallpaper briefly before screen blank.
* screen blank
* wake with space bar
* see lock screen wallpaper, not a white background
* login
* all windows still open as before

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gdm3 3.26.0-1ubuntu1
Uname: Linux 4.13.0-041300-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 14 21:18:20 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-09-09 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170906)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Do you have any relevant crash files in /var/crash/ ?

If so, please upload them with this command:

  ubuntu-bug /var/crash/YOURFILE.crash

[hamid (alias-neo-one)]

My Ryzen CPU is with AMD on RMA at the moment, I will attempt to add this once my PC has its brain back.

I would like to add, in case it may be relevent; I tested Wayland to fix the HIDPI bug, Wayland behaves slightly worse than Xorg in that once locked the pc never wakes again without a power cycle.

[Ritserveldt (muffinzor)]

I'm having the same issue.
I tried using ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash
but then I get an ubuntu has experienced an internal error pop-up and the command hangs.

[Chris S. (r-chris-2)]

This happened to me too, and I've noticed the screen flash on occasion. No graphics card.

12:03:06 PM gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
12:03:06 PM gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
12:02:59 PM gnome-session-b: CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling StartServiceByName for org.gnome.ScreenSaver: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.ScreenSaver exited with status 1
12:02:58 PM gnome-session-b: Unrecoverable failure in required component org.gnome.Shell.desktop