The lines with (EE) are errors from the Xwayland process. And if Xwayland goes down then so does gnome-shell (bug 1505409, bug 1556601). Your logs show your session crash is superficially one of those two bugs:
Oct 30 05:46:19 username-SP4 gnome-shell[7083]: Connection to xwayland lost However the root cause is the Xwayland crash so let's make this bug about the Xwayland crash. It sounds a known issue here... https://phabricator.freedesktop.org/T7722 ** Package changed: gnome-shell (Ubuntu) => xorg-server (Ubuntu) ** Tags added: xwayland ** Summary changed: - session crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 + Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1728588 Title: Xwayland crashed with wl_registry@2: error 0: invalid global wl_output (36) after kernel: [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 Status in xorg-server package in Ubuntu: New Bug description: I turned off my screen for a few hours then turned it on again and my session was no longer there and i had to login again. The following lines from syslog at the time that i turned on the screen again look suspicious. My hypothesis is that the error from the Intel kernel driver caused the "Fatal server error" "wl_registry@2: error 0: invalid global wl_output (36)" in gnome-shell. Since the screen is actually still operational (after all, the computer didn't crash, only that session, and i was immediately shown the login screen and able to login again), what should have happened is that gnome- shell should have gracefully dealt with whatever happened without a fatal error. This is the first time this has happened, and it did not used to happen before my upgrade to Artful a few days ago. Oct 30 05:46:16 bshanks-SP4 kernel: [358036.641989] [drm:intel_mst_disable_dp [i915]] *ERROR* failed to update payload -22 Oct 30 05:46:16 bshanks-SP4 gnome-shell[7083]: WARNING: addSignalMethods is replacing existing [0x5563dd13c c40 Gjs_ShowAppsIcon.dash-item-container] connect method ... (a bunch of similar warnings about addSignalMethods) ... Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: Fatal server error: Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) wl_registry@2: error 0: invalid global wl_output (36) Oct 30 05:46:18 bshanks-SP4 org.gnome.Shell.desktop[7083]: (EE) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 30 06:01:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2016-04-06 (572 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-26 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1728588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp

