gnome-shell crashed with signal 5

[Paul White]

I was informed by the relevant GNOME Shell extension that an update was available for Dash to Dock. I went to extensions.gnome.org to update it. The new version downloaded but my computer froze.

I waited for GNOME Shell to recover which it did after a minute or so. The extension was switched off so I turned it on which prompted another download. The extension was then shown as having an error.

I restarted GNOME Shell with "Alt+F2 >> r and enter" and shortly after received a prompt to report an issue which is what I am doing.

Normal functionality with respect to turning the Dash to dock extension on and off has now resumed.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Sun Jun 10 10:03:51 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-11-07 (214 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_value () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_settings_get_boolean () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: gnome-shell crashed with signal 5
UpgradeStatus: Upgraded to cosmic on 2018-02-21 (108 days ago)
UserGroups: adm cdrom dip kvm lpadmin 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 #1748450, 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.