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()

Bug #1859259 reported by Asif Youssuff on 2020-01-11
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Fix Released
gnome-shell (Ubuntu)
mutter (Ubuntu)

Bug Description


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
 PATH=(custom, user)
RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1
 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
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
 ?? () from /lib/x86_64-linux-gnu/
Title: gnome-shell crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

Asif Youssuff (yoasif) wrote :

 meta_surface_actor_get_texture (self=self@entry=0x0) at ../src/compositor/meta-surface-actor.c:334
 meta_wayland_actor_surface_real_sync_actor_state (actor_surface=0x7fa52033fb00) at ../src/wayland/meta-wayland-actor-surface.c:155
 meta_wayland_subsurface_sync_actor_state (actor_surface=0x7fa52033fb00) at ../src/wayland/meta-wayland-subsurface.c:278
 meta_wayland_actor_surface_sync_actor_state (actor_surface=<optimized out>) at ../src/wayland/meta-wayland-actor-surface.c:238
 meta_wayland_actor_surface_real_sync_actor_state (actor_surface=<optimized out>) at ../src/wayland/meta-wayland-actor-surface.c:228

Changed in gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
summary: - gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
+ from meta_wayland_actor_surface_real_sync_actor_state()
information type: Private → Public
Changed in gnome-shell (Ubuntu):
status: New → Confirmed
description: updated
tags: added: eoan
Changed in mutter (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Daniel van Vugt (vanvugt) wrote :

It looks like some JavaScript is doing painting here...

#8 0x00007fa5318efa05 in meta_wayland_surface_role_commit (pending=0x555e42fcde50, surface_role=<optimized out>) at ../src/wayland/meta-wayland-surface.h:45
No locals.
#9 meta_wayland_surface_apply_pending_state (surface=0x555e458b8540, pending=0x555e42fcde50) at ../src/wayland/meta-wayland-surface.c:802
        had_damage = 1
        __func__ = "meta_wayland_surface_apply_pending_state"
#10 0x00007fa53093a81e in ffi_call_unix64 () at ../src/x86/unix64.S:76
No locals.
#11 0x00007fa53093a1ef in ffi_call (cif=cif@entry=0x7ffde18c88f0, fn=<optimized out>, rvalue=<optimized out>, rvalue@entry=0x0, avalue=avalue@entry=0x7ffde18c89c0) at ../src/x86/ffi64.c:525

So that sounds like a buggy extension more than a Gnome Shell issue. You also have a few extensions installed:

'<email address hidden>'
'<email address hidden>'
'<email address hidden>'
'<email address hidden>'
'<email address hidden>'

Please try UNINSTALLING those. I suspect BingWallpaper the most since it would do rendering, and it shows up in your system log with errors too.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Incomplete
Changed in mutter (Ubuntu):
status: Confirmed → Incomplete
Asif Youssuff (yoasif) wrote :

Okay, looks like my new bug in 1859890 was closed as a duplicate.

As I mentioned in that bug, I both removed the extensions mentioned *and* disabled extensions entirely in GNOME Tweak. I ran into the bug in 1859890.

Hopefully that gives you some more information and shows that the issue exists in plain GNOME, not just when add-ons are installed.

Daniel van Vugt (vanvugt) wrote :


Please try again. Bug 1859890 says you had the extensions enabled when that crash happened:

b'' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>']"

Assuming you have disabled the extensions then the crash in bug 1859890 might be from before or after you disabled them. So that's kind of good -- there is no evidence of the crash happening WITHOUT the extensions. Please uninstall them and keep them uninstalled. Then let us know about any future crashes.

Asif Youssuff (yoasif) wrote :


The first line in GsettingsChanges.txt says:

b'' b'disable-user-extensions' b'true'

I globally disabled extensions via GNOME Tweak -- does this switch not work?

I just now also removed everything inside of /home/asif/.local/share/gnome-shell/extensions -- there was only one extension there (but it should have been disabled anyway).

Daniel van Vugt (vanvugt) wrote :

The GSettingsChanges.txt in this bug and bug 1859890 both say you had at the time of the crashes:

b'' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>']"

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: gnome-shell crashed with SIGSEGV in meta_surface_actor_get_texture()
- from meta_wayland_actor_surface_real_sync_actor_state()
+ from meta_wayland_actor_surface_real_sync_actor_state() from
+ meta_wayland_subsurface_sync_actor_state()
Daniel van Vugt (vanvugt) wrote :

The uncommon thing might be subsurfaces:


which would be triggered by MOZ_ENABLE_WAYLAND=1. So maybe extensions are not involved. We should wait and get a clean crash report from your system while no extensions are installed, to be completely sure.

I still can't find any other reports of this crash from other people in Ubuntu or upstream :/

Asif Youssuff (yoasif) wrote :

This crash just happened: 1859911

I still see those errant extensions inside of GsettingsChanges.txt, but they don't appear in the GNOME Tweak UI, nor do I see them in /home/asif/.local/share/gnome-shell/extensions

I have no idea where they are on disk, and I would be happy to remove them from disk if I knew where they were.

I also don't see them installed via apt.

I went ahead and reset the key via dconf-editor since it seems like those are stale entries, so new crashes shouldn't have that set and confound the situation.

Asif Youssuff (yoasif) wrote :

Also rebooting my machine after resetting the key so extensions should not be enabled after this for sure.

Asif Youssuff (yoasif) wrote :

Please see bug 1859924.

GsettingsChanges.txt doesn't show any enabled extensions.

Daniel van Vugt (vanvugt) wrote :

Perfect, thanks. It's now conclusive that extensions are not the problem.

Given the stack trace mentions Wayland subsurfaces I guess you're just the first to hit this crash.

Next please try avoiding MOZ_ENABLE_WAYLAND=1

Also note that upstream the mutter maintainer has been rewriting the Wayland subsurfaces code recently. This might mean it's a recent regression in 3.34.3, or it might mean this issue has already been fixed in 3.35 (which you can't try yet, sorry).

Changed in gnome-shell (Ubuntu):
status: Incomplete → New
Changed in mutter (Ubuntu):
status: Incomplete → New
tags: added: wayland
tags: added: fixed-in-3.35.4 fixed-upstream
Changed in gnome-shell (Ubuntu):
status: New → Triaged
Changed in mutter (Ubuntu):
status: New → Triaged
Changed in mutter:
status: Unknown → Fix Released
tags: added: fixed-in-3.34.4
Changed in gnome-shell (Ubuntu):
status: Triaged → In Progress
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.