gnome-shell crashed with signal 5

[Mariano Jara Melagrani]

I was testing some new Gnome-shell-extensions and immediately after having enabled one extension called "dashtodock" the system froze and I had to reboot via a tty.

:~$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10

:~$ apt-cache policy gnome-shell-extension-dashtodock
gnome-shell-extension-dashtodock:
  Installed: 61-1
  Candidate: 61-1
  Version table:
 *** 61-1 500
        500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
        500 http://archive.ubuntu.com/ubuntu artful/universe i386 Packages
        100 /var/lib/dpkg/status

I was expecting to enable and test some Gnome-shell-extensions, but after trying the one called "dashtodock" the system came to a halt and I had to login via tty and reboot.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 23 22:09:10 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2016-08-07 (442 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/bin/gnome-shell
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 artful on 2017-10-22 (1 days ago)
UserGroups: adm cdrom dip kismet lpadmin lxd netdev plugdev sambashare sudo wireshark

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