gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from st_theme_node_get_text_shadow() from st_theme_node_get_text_shadow()...

[Ivan Matyunin]

I can't really pinpoint the cause because I've had lots of gnome-shell crashes during normal use and I can't very well tell them apart.

One more-common factor is clicking the top-bar, either when logged in or when the screen is locked.

ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu25
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 9 19:22:24 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fa8144449f2 <st_theme_node_lookup_shadow+146>: mov (%rax),%rdi
 PC (0x7fa8144449f2) ok
 source "(%rax)" (0x223d657079742000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 st_theme_node_lookup_shadow () from /usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /usr/lib/gnome-shell/libst-1.0.so
Title: gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow()
UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago)
UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 st_theme_node_lookup_shadow () from /tmp/apport_sandbox_l1pfsx5u/usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /tmp/apport_sandbox_l1pfsx5u/usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /tmp/apport_sandbox_l1pfsx5u/usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /tmp/apport_sandbox_l1pfsx5u/usr/lib/gnome-shell/libst-1.0.so
 st_theme_node_get_text_shadow () from /tmp/apport_sandbox_l1pfsx5u/usr/lib/gnome-shell/libst-1.0.so

[Daniel van Vugt (vanvugt)]

This looks like the same crash:

[249197.236306] poseidon gnome-shell[2332287]: GNOME Shell crashed with signal 11
[249197.236306] poseidon gnome-shell[2332287]: == Stack trace for context 0x55a0c8de56b0 ==
[249197.236306] poseidon gnome-shell[2332287]: #0 55a0c9c52538 i resource:///org/gnome/shell/ui/layout.js:320 (151fafaf5448 @ 22)
[249197.236306] poseidon gnome-shell[2332287]: #1 55a0c9c524a8 i resource:///org/gnome/shell/ui/overview.js:564 (9f962e0f6a0 @ 118)
[249197.237460] poseidon gnome-shell[2332287]: #2 55a0c9c52418 i resource:///org/gnome/shell/ui/overview.js:688 (9f962e0fa60 @ 87)
[249197.237460] poseidon gnome-shell[2332287]: #3 7ffde6b7e740 b resource:///org/gnome/shell/ui/panel.js:479 (9f962eb6cb8 @ 131)

[Daniel van Vugt (vanvugt)]

I can't find any other reports of this crash so as a first step please try uninstalling all of these extensions:

'<email address hidden>',
'<email address hidden>',
'<email address hidden>',
'gTile@vibou',
'<email address hidden>'

and then tell us if the problem goes away.

[Ivan Matyunin (sibrus-gmail)]

I never isolated a way to reproduce this bug, and I haven't encountered it again (even with keeping the extensions enabled). In fact generally the gnome-shell crashes have largely stopped. I'm not sure at what point that was, but for at least the past few days, things that would often crash gnome-shell no longer cause crashes (such as clicking the top-bar widgets on the lock screen, which before reliably triggered https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868440).

[Daniel van Vugt (vanvugt)]

Let's assume it was bug 1880218

[Daniel van Vugt (vanvugt)]

Actually it is reported here:

https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2493