Here is the backtrace and registers. At first I couldn't reproduce the bug by just moving youtube videos (in firefox) around. But then when I had a document in LibreOffice Writer open (which is the situation I was in over the last few days of crashes), it happened very easily. --- Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault. 0x00007f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 (gdb) bt #0 0x00007f6555da3624 in wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 #1 0x00007f65563fe3f9 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #2 0x00007f65563ff413 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #3 0x00007f6556420110 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #4 0x00007f65563dee69 in ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #5 0x00007f6555ff0f6f in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #6 0x00007f6555ff135a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #7 0x00007f6555fb9094 in gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #8 0x00007f6555ff1006 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #9 0x00007f6556ef0fbd in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x00007f6556ef1240 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x00007f6556ef1533 in g_main_loop_run () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x00007f65563bb970 in meta_run () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 #13 0x0000560782a19d85 in ?? () #14 0x00007f655613d1e3 in __libc_start_main (main=0x560782a19930, argc=1, argv=0x7ffe0362fc48, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe0362fc38) at ../csu/libc-start.c:308 #15 0x0000560782a19f5e in ?? () (gdb) info registers rax 0xffffffffffffffb0 -80 rbx 0x56078765c2c0 94590336352960 rcx 0x7 7 rdx 0x5607850dab40 94590297025344 rsi 0x5607857211d0 94590303605200 rdi 0x0 0 rbp 0xffffffff 0xffffffff rsp 0x7ffe0362f698 0x7ffe0362f698 r8 0x7f650c003300 140071969764096 r9 0x56078a5d8740 94590386145088 r10 0x560784463018 94590283952152 r11 0x7ffe0362f538 140728955237688 r12 0x1 1 r13 0x7f650c003350 140071969764176 r14 0x56078765c2c0 94590336352960 r15 0x560784e680b0 94590294458544 rip 0x7f6555da3624 0x7f6555da3624 <wl_resource_get_version+4> eflags 0x10202 [ IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866222 Title: GNOME Shell crashed with signal 11 Status in gnome-shell package in Ubuntu: Incomplete Bug description: gnome-shell has crashed twice on me today. Unfortunately there's nothing in /var/crash. There's nothing in the journalctl log prior to the crash that explains it. I've attached a log of everything between when the crash happened and when I logged back in (though I suspect most of it is not relevant). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 13:04:21 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-16 (201 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-01-31 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
