Hi,
What you logs tells is:
On Wed, Jan 31, 2018 at 10:37 AM, Howard Howell <hlhowell(a)pacbell.net>
wrote:
Jan 31 01:14:08 school evolution-alarm[2297]: Error reading events
from
display: Broken pipe
Jan 31 01:14:08 school gnome-software[2301]: Error reading events from
display: Broken pipe
Wayland native applications exiting with broken pipe, means the Wayland
compositor (gnome-shell is dead)
Jan 31 01:14:08 school gnome-session-binary[1715]: WARNING: App
'org.gnome.Shell.desktop' exited with code 1
gnome-session tells us that gnome-shell is gone
Jan 31 01:14:08 school gnome-session[1715]:
gnome-session-binary[1715]:
WARNING: App 'org.gnome.Shell.desktop' exited with
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Window manager
error: Could not find cursor. Perhaps set XCURSOR_PATH
Interesting, that could be the problem! gnome-shell is both a Wayland
compositor (thus the display server) and an X11 window manager.
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: Fatal server
error:
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE) failed to read
Wayland events: Broken pipe
Jan 31 01:14:08 school org.gnome.Shell.desktop[1785]: (EE)
Then Xwayland exits with “broken pipe”, like the other Wayland clients,
because the Wayland compositor is, well ,dead.
Jan 31 01:14:08 school gnome-session-binary[1715]: Unrecoverable
failure
in required component org.gnome.Shell.desktop
gnome-session says something goes really wrong...
Jan 31 01:14:08 school
org.gnome.SettingsDaemon.MediaKeys.desktop[2048]:
xcb_connection_has_error() returned true
Jan 31 01:14:08 school gsd-housekeepin[2045]: gsd-housekeeping: Fatal IO
error 11 (Resource temporarily unavailable) on X s
Jan 31 01:14:08 school gsd-print-notif[2013]: gsd-print-notifications:
Fatal IO error 11 (Resource temporarily unavailable)
Jan 31 01:14:08 school at-spi-bus-launcher[1825]: XIO: fatal IO error 11
(Resource temporarily unavailable) on X server ":
ESCOC
And now, the X11 clients (hence depending on the X server, thus Xwayland)
all quit as well, because the X server (Xwayland) is dead, because the
Wayland compositor is dead...
This doesn't tell me anything, but I'll bet some of you
systems guys can
see through it to see the root cause, or at least a good trail to follow.
I think we should keep those discussions, including these important bits,
in the issue you filed upstream (
https://gitlab.gnome.org/GNOME/gnome-shell/issues/9) and not in a
downstream mailing list :)
Cheers,
Olivier