Version-Release number of selected component: xorg-x11-server-Xwayland-1.19.3-4.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /home/mcatanzaro/Projects/GNOME/install/bin/Xwayland :1 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 crash_function: xwl_read_events executable: /usr/bin/Xwayland journald_cursor: s=ca44c691f28b4a3fa6affd95ab5151f5;i=1b36b7;b=1bb81d6006b3438f9124fe2aa5b58740;m=a0fe9fcbc;t=55ce29a097191;x=9b45217435b11c67 kernel: 4.13.9-200.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000
Created attachment 1350099 [details] File: backtrace
Created attachment 1350100 [details] File: cgroup
Created attachment 1350101 [details] File: core_backtrace
Created attachment 1350102 [details] File: cpuinfo
Created attachment 1350103 [details] File: dso_list
Created attachment 1350104 [details] File: environ
Created attachment 1350105 [details] File: limits
Created attachment 1350106 [details] File: maps
Created attachment 1350107 [details] File: open_fds
Created attachment 1350108 [details] File: proc_pid_status
Created attachment 1350109 [details] File: var_log_messages
Same as bug 1510078, this is a abort() because Xwayland (Wayland client) cannot read events from the Wayland compositor (gnome-shell.mutter, presumably) which is most likely a crash in gnome-shell/mutter in the first place. xwl_read_events() aborts in two cases, either it fails to read the events (wl_display_read_events) or it fails to dispatch the events (wl_display_dispatch_pending), in both cases it's a communication issue with the Wayland compositor. Can you quickly check in the logs at the time of the crash if gnome-shell/mutter had crashed or failed to start (I've seen this happening as well at startup, gnome-shell starts, spawns Xwayland, then fails, and Xwayland aborts in xwl_read_events())
I am also experiencing this on Fedora 27, 4.14.0-1, Nouveau, t I think you're right Olivier, this is likely from a crash in mutter: I see in the logs: gnome-shell: segfault at ... in libmutter-1.so.0.0.0... gnome-logs: Error reading events from display: Connection reset by peer kernel: (EE) Xwayland: ANOM_ABEND ... gnome-session-b: gnome-session-binary: WARNING: Application 'org.gnome.Shell.desktop' killed by signal 11 (stack trace...) systemd:coredum: Process 2515 (gnome-shell) of user 1000 dumped core. The stack trace has: #0 and #1 in libc.so.6 #2 OsAbort (Xwayland) #3 AbortServer (Xwayland) #4 FatalError (Xwayland) #5 xwl_read_events (Xwayland) #6 ospoll_wait (Xwayland) I haven't been able to determine if some user action causes this. It seems to happen when I have the screen off (perhaps a notification triggers this crash? or turning the screen on, which activates the Displayport link, triggers the crash?) I have mutter and gnome-shell at 3.26.2-1, and gnome-session(-xsession, -wayland-session) at 3.26.1-1. Please let me know what more would be useful.
Maybe that is related to my issue Bug 1513807 ?
I was also experiencing this same problem after fresh install of Fedora 27. The problem is easily and always reproducible. The steps are : 1. login properly 2. power off monitor (or wait until screen saver cause the monitor to auto-sleep) 3. power back on the monitor (or wake-up from monitor sleep mode) It reports "gnome-shell" was crashed and I have to re-login again. I used just an ordinary HDMI full-HD monitor. This always happens, even just after fresh reboot. Should be something when the HDMI connection back on caused something to crash.
This is simply Xwayland telling your Wayland compositor (namely gnome-shell/mutter) has died. Basically, gnome-shell (now) runs Xwayland with “-core” which means that *any* FatalError() in Xwayland will dump a core file. xwl_read_events() triggers a FatalError() because the Wayland socket is unusable, and it's unusable because the Wayland compositor (the other side of the socket) has died, i.e. crashed most likely. The Wayland compositor is gnome-shell/mutter, so if you could please look into journalctl and coredumpctl to find a backtrace and/or generate one with coredumpctl and gdb. From comment 15, this is most likely a dupe of bug 1500325.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.