gnome-shell segfaults in Wayland when display is turned off while Kodi running

Asked by Frank Feuerbacher

Testing Kodi 18.0-BETA1 Git:20180828-f21b477 on Ubuntu 18.04 running Wayland gnome-shell. Everything is fine, however, whenever I turn the display off and leave Kodi running, then gnome-shell segfaults and my session is killed.

Here is a portion of syslog:

<code>
Aug 30 12:31:28 smeagol kernel: [ 7377.674305] snd_hda_intel 0000:00:03.0: spurious response 0x0:0x0, last cmd=0x773452
Aug 30 12:31:28 smeagol kernel: [ 7377.724872] gnome-shell[2007]: segfault at 18 ip 00007fc15b4751e6 sp 00007ffe24099360 error 4 in libmutter-2.so.0.0.0[7fc15b392000+157000]
Aug 30 12:31:28 smeagol boinc[1532]: No protocol specified
Aug 30 12:31:29 smeagol gnome-control-c[10533]: Error reading events from display: Broken pipe
Aug 30 12:31:29 smeagol dropbox[2513]: Error reading events from display: Broken pipe
Aug 30 12:31:29 smeagol gnome-terminal-[2721]: Error reading events from display: Broken pipe
Aug 30 12:31:29 smeagol kodi.desktop[14642]: terminate called after throwing an instance of 'std::runtime_error'
Aug 30 12:31:29 smeagol telepathy-indic[2635]: Error reading events from display: Broken pipe
Aug 30 12:31:29 smeagol psensor[2770]: Error reading events from display: Broken pipe
Aug 30 12:31:29 smeagol solaar[2479]: Error reading events from display: Broken pipe
Aug 30 12:31:29 smeagol systemd[1773]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE
Aug 30 12:31:29 smeagol systemd[1773]: gnome-terminal-server.service: Failed with result 'exit-code'.
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: (EE)
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: Fatal server error:
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: (EE) failed to read Wayland events: Connection reset by peer
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: (EE)
Aug 30 12:31:29 smeagol kodi.desktop[14642]: terminate called recursively
Aug 30 12:31:29 smeagol gsd-media-keys[2321]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 30 12:31:29 smeagol gsd-keyboard[2313]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 30 12:31:29 smeagol gsd-power[2344]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: Gdk-Message: 12:31:29.282: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: Gdk-Message: 12:31:29.282: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: xcb_connection_has_error() returned true
Aug 30 12:31:29 smeagol gnome-session-binary[1901]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
Aug 30 12:31:29 smeagol gnome-session[1901]: gnome-session-binary[1901]: WARNING: App 'org.gnome.SettingsDaemon.Keyboard.desktop' exited with code 1
Aug 30 12:31:29 smeagol gsd-color[2308]: gsd-color: Fatal IO error 104 (Connection reset by peer) on X server :0.
Aug 30 12:31:29 smeagol kernel: [ 7378.742095] Chrome_~dThread[3037]: segfault at 0 ip 00007f77b244ffdd sp 00007f77b08aab00 error 6 in libxul.so[7f77b1770000+5f99000]
Aug 30 12:31:29 smeagol pulseaudio[14867]: [pulseaudio] client-conf-x11.c: xcb_connection_has_error() returned true
Aug 30 12:31:29 smeagol org.gnome.Shell.desktop[2007]: Sandbox: Unexpected EOF, op 2 flags 00 path /etc/localtime
Aug 30 12:31:29 smeagol at-spi-bus-launcher[2181]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Aug 30 12:31:29 smeagol at-spi-bus-launcher[2181]: after 4679 requests (4679 known processed) with 0 events remaining.
<\code>

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 30 13:16:57 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2012-12-31 (2067 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to bionic on 2018-08-21 (9 days ago)

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu gnome-shell Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Frank Feuerbacher (drw06g0w7-frank) said :
#1

There appears to be no way to report a Wayland / gnome-shell crash. I can create the .crash files, but they are never uploaded. I have spent over 8 hours trying to do this but none of the suggestions have worked. I think the bug reporting tools are broken for Wayland, but I am tired of fighting it.

Revision history for this message
Launchpad Janitor (janitor) said :
#2

This question was expired because it remained in the 'Open' state without activity for the last 15 days.