gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()

[hackel]

Hard crash, Wayland session dies completely. Possible dupe of #1714745. I wasn't doing anything at the time. Had Firefox open. Went to move the cursor and realized it was frozen (presumably while saving the .crash file), and then it exited back to the login screen.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.13.0-30.33-generic 4.13.13
Uname: Linux 4.13.0-30-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Jan 20 23:28:23 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1510175942
InstallationDate: Installed on 2017-12-09 (42 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /home/hackel
SegvAnalysis:
 Segfault happened at: 0x7f279523ede2 <g_type_check_instance_cast+34>: mov (%rdi),%rbp
 PC (0x7f279523ede2) ok
 source "(%rdi)" (0x9000000084) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_type_check_instance_cast () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 st_label_set_text () from /usr/lib/gnome-shell/libst-1.0.so
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ?? () from /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_cast()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

[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 #1714989, 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.