FS#60131 - [mutter] Crash on startup with lid closed

Attached to Project: Arch Linux
Opened by Ferran Pallarès (poinu) - Thursday, 20 September 2018, 07:20 GMT
Last edited by Jan de Groot (JGC) - Thursday, 11 October 2018, 21:53 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Xwayland crashes during startup when laptop is connected to dock station with the laptop lid closed. Gnome-session crashes too, but it's probably because of the Xwayland crash. This doesn't happen if the laptop lid is open during the startup process.

Additional info:

Package versions:

xorg-server-xwayland 1.20.1-1
gnome-session 3.30.0-1

Journal:

Sep 20 08:52:39 hostname gnome-session-binary[6886]: Unrecoverable failure in required component org.gnome.Shell.desktop
Sep 20 08:52:39 hostname systemd-coredump[7374]: Process 7086 (gnome-shell) of user 1000 dumped core.

Stack trace of thread 7086:
#0 0x00007fade86c52e0 meta_logical_monitor_get_layout (libmutter-3.so.0)
#1 0x00007fade875dea5 n/a (libmutter-3.so.0)
#2 0x00007fade6a8a1c8 ffi_call_unix64 (libffi.so.6)
#3 0x00007fade6a89c2a ffi_call (libffi.so.6)
#4 0x00007fade38786ff n/a (libwayland-server.so.0)
#5 0x00007fade38750a3 n/a (libwayland-server.so.0)
#6 0x00007fade3876702 wl_event_loop_dispatch (libwayland-server.so.0)
#7 0x00007fade8741d59 n/a (libmutter-3.so.0)
#8 0x00007fade92873cf g_main_context_dispatch (libglib-2.0.so.0)
#9 0x00007fade9288f89 n/a (libglib-2.0.so.0)
#10 0x00007fade9289f62 g_main_loop_run (libglib-2.0.so.0)
#11 0x00007fade8743004 meta_xwayland_start (libmutter-3.so.0)
#12 0x00007fade87423e3 meta_wayland_init (libmutter-3.so.0)
#13 0x00007fade8708229 meta_init (libmutter-3.so.0)
#14 0x000055e0ecf4f138 n/a (gnome-shell)
#15 0x00007fade97a6223 __libc_start_main (libc.so.6)
#16 0x000055e0ecf4f50e n/a (gnome-shell)

Stack trace of thread 7106:
#0 0x00007fade9872bb1 __poll (libc.so.6)
#1 0x00007fade9288ee0 n/a (libglib-2.0.so.0)
#2 0x00007fade9288fce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fade9289022 n/a (libglib-2.0.so.0)
#4 0x00007fade92523eb n/a (libglib-2.0.so.0)
#5 0x00007fade994da9d start_thread (libpthread.so.0)
#6 0x00007fade987da43 __clone (libc.so.6)

Stack trace of thread 7108:
#0 0x00007fade9872bb1 __poll (libc.so.6)
#1 0x00007fade9288ee0 n/a (libglib-2.0.so.0)
#2 0x00007fade9289f62 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007fade93eec28 n/a (libgio-2.0.so.0)
#4 0x00007fade92523eb n/a (libglib-2.0.so.0)
#5 0x00007fade994da9d start_thread (libpthread.so.0)
#6 0x00007fade987da43 __clone (libc.so.6)

Stack trace of thread 7112:
#0 0x00007fade987840d syscall (libc.so.6)
#1 0x00007fade9237f61 g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007fade92b5cb3 n/a (libglib-2.0.so.0)
#3 0x00007fade9259d2b n/a (libglib-2.0.so.0)
#4 0x00007fade92523eb n/a (libglib-2.0.so.0)
#5 0x00007fade994da9d start_thread (libpthread.so.0)
#6 0x00007fade987da43 __clone (libc.so.6)

Stack trace of thread 7233:
#0 0x00007fade9953afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007fadd83f2f3c n/a (i965_dri.so)
#2 0x00007fadd83f2c78 n/a (i965_dri.so)
#3 0x00007fade994da9d start_thread (libpthread.so.0)
#4 0x00007fade987da43 __clone (libc.so.6)

Stack trace of thread 7113:
#0 0x00007fade9872bb1 __poll (libc.so.6)
#1 0x00007fade9288ee0 n/a (libglib-2.0.so.0)
#2 0x00007fade9288fce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007fade996fbde n/a (libdconfsettings.so)
#4 0x00007fade92523eb n/a (libglib-2.0.so.0)
#5 0x00007fade994da9d start_thread (libpthread.so.0)
#6 0x00007fade987da43 __clone (libc.so.6)
Sep 20 08:52:40 hostname systemd-coredump[7670]: Process 7364 (Xwayland) of user 1000 dumped core.

Stack trace of thread 7364:
#0 0x00007fb9bbcbfd7f raise (libc.so.6)
#1 0x00007fb9bbcaa672 abort (libc.so.6)
#2 0x000055e3a47cd05a n/a (Xwayland)
#3 0x000055e3a47c5425 n/a (Xwayland)
#4 0x000055e3a48ec3ec n/a (Xwayland)
#5 0x00007fb9bb59af4a n/a (libwayland-client.so.0)
#6 0x00007fb9bb596c98 wl_proxy_marshal_array_constructor_versioned (libwayland-client.so.0)
#7 0x00007fb9bb596f0c wl_proxy_marshal_constructor (libwayland-client.so.0)
#8 0x00007fb9bb597ff8 wl_display_roundtrip_queue (libwayland-client.so.0)
#9 0x000055e3a48f2c0c n/a (Xwayland)
#10 0x000055e3a478fd78 n/a (Xwayland)
#11 0x00007fb9bbcac223 __libc_start_main (libc.so.6)
#12 0x000055e3a479213e n/a (Xwayland)
Sep 20 08:52:41 hostname gnome-session-binary[747]: Unrecoverable failure in required component org.gnome.Shell.desktop
Sep 20 08:52:41 hostname systemd-coredump[7939]: Process 1063 (Xwayland) of user 120 dumped core.

Stack trace of thread 1063:
#0 0x00007f87beaa9d7f raise (libc.so.6)
#1 0x00007f87bea94672 abort (libc.so.6)
#2 0x000056404477605a n/a (Xwayland)
#3 0x000056404476e425 n/a (Xwayland)
#4 0x00005640448953ec n/a (Xwayland)
#5 0x00007f87be384e8a n/a (libwayland-client.so.0)
#6 0x00007f87be3801f9 n/a (libwayland-client.so.0)
#7 0x00007f87bce891c8 ffi_call_unix64 (libffi.so.6)
#8 0x00007f87bce88c2a ffi_call (libffi.so.6)
#9 0x00007f87be383f5f n/a (libwayland-client.so.0)
#10 0x00007f87be3806ca n/a (libwayland-client.so.0)
#11 0x00007f87be381bdf wl_display_dispatch_queue_pending (libwayland-client.so.0)
#12 0x0000564044896bdb n/a (Xwayland)
#13 0x0000564044777dd1 n/a (Xwayland)
#14 0x000056404483fad0 n/a (Xwayland)
#15 0x000056404473a10d n/a (Xwayland)
#16 0x00007f87bea96223 __libc_start_main (libc.so.6)
#17 0x000056404473b13e n/a (Xwayland)

Stack trace of thread 1078:
#0 0x00007f87bd783afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f87ba66cf3c n/a (i965_dri.so)
#2 0x00007f87ba66cc78 n/a (i965_dri.so)
#3 0x00007f87bd77da9d start_thread (libpthread.so.0)
#4 0x00007f87beb6da43 __clone (libc.so.6)

Stack trace of thread 1176:
#0 0x00007f87bd783afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f87b89e3054 n/a (swrast_dri.so)
#2 0x00007f87b89e2f98 n/a (swrast_dri.so)
#3 0x00007f87bd77da9d start_thread (libpthread.so.0)
#4 0x00007f87beb6da43 __clone (libc.so.6)

Stack trace of thread 1174:
#0 0x00007f87bd783afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f87b89e3054 n/a (swrast_dri.so)
#2 0x00007f87b89e2f98 n/a (swrast_dri.so)
#3 0x00007f87bd77da9d start_thread (libpthread.so.0)
#4 0x00007f87beb6da43 __clone (libc.so.6)

Stack trace of thread 1177:
#0 0x00007f87bd783afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f87b89e3054 n/a (swrast_dri.so)
#2 0x00007f87b89e2f98 n/a (swrast_dri.so)
#3 0x00007f87bd77da9d start_thread (libpthread.so.0)
#4 0x00007f87beb6da43 __clone (libc.so.6)

Stack trace of thread 1175:
#0 0x00007f87bd783afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f87b89e3054 n/a (swrast_dri.so)
#2 0x00007f87b89e2f98 n/a (swrast_dri.so)
#3 0x00007f87bd77da9d start_thread (libpthread.so.0)
#4 0x00007f87beb6da43 __clone (libc.so.6)

Steps to reproduce:

Boot laptop with wayland (and gnome-session?), while having lid closed and connected to an external monitor.

This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 11 October 2018, 21:53 GMT
Reason for closing:  Fixed
Comment by Ferran Pallarès (poinu) - Thursday, 20 September 2018, 07:26 GMT
Forgot to add kernel version: Linux host 4.18.8-arch1-1-ARCH #1 SMP PREEMPT Sat Sep 15 20:34:48 UTC 2018 x86_64 GNU/Linux
Comment by Jan de Groot (JGC) - Thursday, 20 September 2018, 07:48 GMT
XWayland dies because of an assertion. The real crash is in mutter that fails to initialize monitor layout.
Comment by Ferran Pallarès (poinu) - Thursday, 20 September 2018, 11:54 GMT
Oh I see, sorry for the confusion...
Comment by Thomas Andersson (toandersson) - Thursday, 27 September 2018, 05:12 GMT
I have exactly the same problem with my Lenovo Thinkpad T470p. I have a Lenovo Thinkpad Ultra Dock with two monitors attached via DisplayPort.
It seems like the issue started after upgrading to gnome-shell-3.30

gnome-shell 3.30.0+37+g969eecb88-1
mutter 3.30.0+13+g2fb3db765-1
wayland 1.16.0-1
xorg-server-xwayland 1.20.1-1
linux-lts 4.14.72-1
Comment by Thomas Andersson (toandersson) - Thursday, 11 October 2018, 10:02 GMT
This problem seems to have disappeared now after I upgraded to:
gnome-shell 1:3.30.1-1
mutter 3.30.1-1

Loading...