Version-Release number of selected component:
cmdline: /usr/bin/Xwayland :1 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6
pkg_fingerprint: 199E 2F91 FD43 1D51
pkg_vendor: Red Hat, Inc.
reproducible: Not sure how to reproduce the problem
runlevel: N 5
Thread no. 1 (6 frames)
#5 xwl_read_events at xwayland.c:594
#6 ospoll_wait at ospoll.c:412
#7 WaitForSomething at WaitFor.c:226
#8 Dispatch at dispatch.c:422
#9 dix_main at main.c:287
Created attachment 1367329 [details]
Most probably dup of bz1516408
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.
(In reply to Tomas Pelka from comment #3)
> Most probably dup of bz1516408
Matěj said on irc he's using mutter-3.26.2-6 which contanis the fix for bug 1516408, so it's a different issue.
We'll need the backtrace of gnome-shell for sure.
Created attachment 1367436 [details]
output of journalctl -xb
coredumpctl is completely silent.
core.13028: ELF 64-bit LSB core file x86-64, version 1 (SYSV), too many program header sections (2128)
core.13323: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/Xwayland :1 -rootless -terminate -core -listen 4 -listen 5 -displayfd', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/bin/Xwayland', platform: 'x86_64'
The second coredump is apparently the one we have backtrace from, but the other one is a myster (it has 1.1G, so it is by far not empty).
From attachment 1367436 [details] :
Dec 13 13:27:50 mitmanek.ceplovi.cz kernel: traps: gnome-shell general protection ip:7f1d1f8f8bc0 sp:7fff91fcb1e0 error:0 in libgobject-2.0.so.0.5400.2[7f1d1f8c6000+4f000]
Dec 13 13:27:50 mitmanek.ceplovi.cz abrt-hook-ccpp: Process 13028 (gnome-shell) of user 1000 killed by SIGSEGV - dumping core
Dec 13 13:27:59 mitmanek.ceplovi.cz abrt-hook-ccpp: /var/spool/abrt is 5076597800 bytes (more than 1279MiB), deleting 'ccpp-2017-12-13-13:23:24-17860'
Dec 13 13:27:59 mitmanek.ceplovi.cz abrt-server: Package 'gnome-shell' isn't signed with proper key
Unfortunately, that doesn't tell us much on the root cause of the crash...
Created attachment 1367491 [details]
Actually, gdb was able to decipher the other coredump and it was truly from gnome-shell.
Oh right! This seems to come from the JS part of gnome-shell, moving to gnome-shell then (apparently unrelated to Wayland).
Backtrace is similar to https://bugzilla.gnome.org/show_bug.cgi?id=788931
(In reply to Olivier Fourdan from comment #11)
> Backtrace is similar to https://bugzilla.gnome.org/show_bug.cgi?id=788931
gjs 1.50.4 should have fixes to avoid crashing in this case. I'd like to get the update into 7.5; it's a minor bug fix release that should help with several gnome-shell crashes.
lmiksik, could you provide pm_ack and exception+ for this, please?
gjs-1.50.4-1.el7 should fix the crash and turn it into a warning in system logs. We should still try to get the gnome-shell fix in though, if possible.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.