[SOLVED] Xwayland crashes when GDM starts

tinybob20 · 2019-03-17 00:01:58

Since I updated around 3/12/19, GDM won't let me log into a wayland session, instead defaulting to X11. I've tracked it down to Xwayland crashing when GDM starts, but I can't figure out how to fix it. I've rolled Xwayland back as far as it can go, but it still crashes so I'm thinking it's some other library. I'm on a 2015 X1 Carbon with intel graphics.
Journalctl:

Mar 16 19:42:15 frontier systemd[1]: Reached target Multi-User System.
Mar 16 19:42:15 frontier systemd[1]: Reached target Graphical Interface.
Mar 16 19:42:15 frontier systemd[1]: Starting TLP system startup/shutdown...
Mar 16 19:42:15 frontier tlp[947]: Applying power save settings...done.
Mar 16 19:42:15 frontier tlp[947]: Setting battery charge thresholds...done.
Mar 16 19:42:15 frontier systemd[1]: Started TLP system startup/shutdown.
Mar 16 19:42:15 frontier systemd[1]: Startup finished in 5.633s (firmware) + 1.773s (loader) + 3.563s (kernel) + 3.510s (userspace) = 14.481s.
Mar 16 19:42:15 frontier audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=tlp comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 16 19:42:15 frontier org.gnome.Shell.desktop[863]: glamor: No eglstream capable devices found
Mar 16 19:42:16 frontier org.gnome.Shell.desktop[863]: (EE)
Mar 16 19:42:16 frontier org.gnome.Shell.desktop[863]: (EE) Backtrace:
Mar 16 19:42:16 frontier audit[1139]: ANOM_ABEND auid=4294967295 uid=120 gid=120 ses=4294967295 pid=1139 comm="Xwayland" exe="/usr/bin/Xwayland" sig=11 res=1
Mar 16 19:42:16 frontier systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Mar 16 19:42:16 frontier audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@0-1141-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=succe>
Mar 16 19:42:16 frontier systemd[1]: Started Process Core Dump (PID 1141/UID 0).
Mar 16 19:42:16 frontier gnome-shell[863]: X Wayland crashed; exiting

Backtrace:

(gdb) thread apply all bt

Thread 2 (Thread 0x7ff3c97fa700 (LWP 7758)):
#0  0x00007ff3cbd15afc in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /usr/lib/libpthread.so.0
#1  0x00007ff3c9f78c94 in ?? () from /usr/lib/dri/i965_dri.so
#2  0x00007ff3c9f789b8 in ?? () from /usr/lib/dri/i965_dri.so
#3  0x00007ff3cbd0fa9d in start_thread () from /usr/lib/libpthread.so.0
#4  0x00007ff3cc907b23 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7ff3ca8968c0 (LWP 7757)):
#0  x86_64_fallback_frame_state (context=0x7ffd9de89050, 
    context=0x7ffd9de89050, fs=0x7ffd9de89140) at ./md-unwind-support.h:63
#1  uw_frame_state_for (context=context@entry=0x7ffd9de89050, 
    fs=fs@entry=0x7ffd9de89140) at /build/gcc/src/gcc/libgcc/unwind-dw2.c:1265
#2  0x00007ff3ca88da38 in _Unwind_Backtrace (
    trace=0x7ff3cc915b40 <backtrace_helper>, trace_argument=0x7ffd9de89300)
    at /build/gcc/src/gcc/libgcc/unwind.inc:302
#3  0x00007ff3cc915cc6 in backtrace () from /usr/lib/libc.so.6
#4  0x00005620c1068d1d in ?? ()
#5  0x00005620c1069730 in ?? ()
#6  <signal handler called>
#7  0x00007ff3c104daac in ?? () from /usr/lib/libLLVM-7.so
#8  0x000000000000001c in ?? ()
--Type <RET> for more, q to quit, c to continue without paging--
#9  0x00007ffd9de89d30 in ?? ()
#10 0x0000000000000030 in ?? ()
#11 0x0000000000000007 in ?? ()
#12 0x0000000000000003 in ?? ()
#13 0x00005620c2ceb018 in ?? ()
#14 0x000000000000001f in ?? ()
#15 0x0000000000000050 in ?? ()
#16 0xffffffffffffffb0 in ?? ()
#17 0x0000000000000000 in ?? ()

Last edited by tinybob20 (2019-03-26 16:49:25)

jasonwryan · 2019-03-17 00:13:55

tinybob20 wrote:

Since I updated around 3/12/19

This is essentially meaningless: please edit your post to include version numbers.

tinybob20 · 2019-03-25 16:55:21

I'm on the most recent gnome release:

gnome-shell: 1:3.32.0+20+g05e55cee2-1
xorg-server-xwayland: 1.20.4-1
gdm: 3.32.0+2+g820f90f5-1

Last edited by tinybob20 (2019-03-25 16:55:58)

tinybob20 · 2019-03-26 16:49:11

Found the issue. llvm-libs 7.0.1-2 is segfaulting, downgrading it solved Xwayland crashes.

I actually found the issue because `ar` was segfaulting too, and libLLVM showed up the dump.

Arch Linux

#1 2019-03-17 00:01:58

[SOLVED] Xwayland crashes when GDM starts

#2 2019-03-17 00:13:55

Re: [SOLVED] Xwayland crashes when GDM starts

#3 2019-03-25 16:55:21

Re: [SOLVED] Xwayland crashes when GDM starts

#4 2019-03-26 16:49:11

Re: [SOLVED] Xwayland crashes when GDM starts

Board footer