On Tue, 02 Jan 2018 at 18:42:00 +0000, Kjö Hansi Glaz wrote: > Actually there are two crashes, which you can find below: > > $ coredumpctl | tee > TIME PID UID GID SIG COREFILE EXE > Tue 2018-01-02 19:18:33 CET 2042 1000 1000 6 present > /usr/bin/Xwayland > Tue 2018-01-02 19:18:33 CET 1981 1000 1000 11 present > /usr/bin/gnome-shell
One of these probably causes the other - it'll be a bug in the error handing code paths of either Xwayland or gnome-shell. > #1 0x00007fe7b7c65278 in st_label_set_text (label=0x558a749ee890 > [StLabel], text=0x558a772bcf90 "76") at ../src/st/st-label.c:331 Does the text "76" mean anything to you? Perhaps it's a battery level or the name of a wireless network near you or something? That would narrow it down a bit... it's hard to tell what caused a crash like this where most of the stack is "interpret JavaScript". > #23 0x00007fe7b13f1040 in js::jit::InvokeFunctionInfo () at > /usr/lib/x86_64-linux-gnu/libmozjs-52.so.0 libmozjs-52-0-dbgsym would provide more information about this part of the stack, although it probably isn't particularly interesting. "thread apply all bt" might also be interesting: that'll tell us which threads were active and which were just waiting. > #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 > #1 0x00007f080f05e19a in __GI_abort () at abort.c:89 > #2 0x00005561bc7418ba in OsAbort () > #3 0x00005561bc7473d3 in ?? () > #4 0x00005561bc7481f5 in FatalError () > #5 0x00005561bc5cf84f in ?? () > #6 0x00005561bc73f371 in ?? () > #7 0x00005561bc73835b in WaitForSomething () > #8 0x00005561bc704193 in ?? () > #9 0x00005561bc708410 in ?? () > #10 0x00007f080f049561 in __libc_start_main (main=0x5561bc5cee60, > argc=11, argv=0x7ffe218ae768, init=<optimized out>, > fini=<optimized out>, rtld_fini=<optimized out>, > stack_end=0x7ffe218ae758) at ../csu/libc-start.c:297 I think this is also missing some debug symbols, but I can't tell which ones; perhaps xwayland-dbgsym if you don't already have that. smcv