The GSettingsChanges.txt in this bug and bug 1859890 both say you had at the time of the crashes:
b'org.gnome.shell' b'enabled-extensions' b"['user-theme@gnome-shell- extensions.gcampax.github.com', 'impatie...@gfxmonk.net', 'no...@maestroschan.fr', 'bingwallpa...@ineffable-gmail.com', 'dayni...@maze-n.github.com']" I'm not sure how effective disable-user-extensions is as we have found in other bug reports that buggy extensions can just ignore the disable setting. Extensions need to be uninstalled to be sure. It is also possible you have disabled extensions successfully and the latest crash dump (bug 1859890) was just sitting on disk from before that time. Hence removing extensions may have successfully stopped the crash from occurring. Let's give it time and see if any more occur. Also worth noting you are the only person reporting this crash right now, which suggests it's caused by something uncommon. ** Summary changed: - gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() + gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state() -- 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/1859259 Title: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture() from meta_wayland_actor_surface_real_sync_actor_state() from meta_wayland_subsurface_sync_actor_state() Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/afac105a2b17f4a362200df1802b62a248fd7bc2 --- This has begun happening in the last few days; I was unable to create a bug for the last crash because I had some outdated packages installed. This crash occurred as I started Firefox Nightly on my machine with a fairly large session being restored. GNOME logged me out as the windows were being spawned by session restored. My Firefox is being started in pure Wayland mode -- MOZ_ENABLE_WAYLAND=1 I am using "Basic" compositing (not WebRender) in this session. Happy to provide any other details. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Jan 10 20:22:13 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-01-05 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200104) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1 SegvAnalysis: Segfault happened at: 0x7fa5318821db: mov (%rdi,%rax,1),%rax PC (0x7fa5318821db) ok source "(%rdi,%rax,1)" (0xfffffffffffffcb0) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-5.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1859259/+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
