gnome-shell crashed with SIGABRT in g_assertion_message_expr()

[El jinete sin cabeza]

Returning hibernating.

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
Uname: Linux 5.0.2-050002-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 16 20:15:43 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
 b'org.gnome.shell' b'enabled-extensions' b"['desktop-icons@csoriano', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
 b'org.gnome.desktop.interface' b'clock-show-weekday' b'true'
InstallationDate: Installed on 2018-12-02 (104 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=es_CL:es
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-4.so.0
 g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: Upgraded to disco on 2018-12-02 (104 days ago)
UserGroups: adm cdrom dip 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 #1820331, 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.