gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()

[Gordon Ball]

ubuntu-bug upload of crash file from discussion in #1871580

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
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 8 13:03:38 2020
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1585586945
InstallationDate: Installed on 2019-05-27 (316 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/gordon
RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fd6a9ce545a <st_theme_node_get_font_features+106>: mov (%rdx),%rsi
 PC (0x7fd6a9ce545a) ok
 source "(%rdx)" (0x4d4952505f535445) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 st_theme_node_get_font_features () at /usr/lib/gnome-shell/libst-1.0.so
 _st_set_text_from_style () at /usr/lib/gnome-shell/libst-1.0.so
 () at /usr/lib/gnome-shell/libst-1.0.so
 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_font_features()
UpgradeStatus: Upgraded to focal on 2020-04-06 (2 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1868440, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.