gnome-shell crashed with signal 5 in g_log_default_handler()

[Ludovic C.]

Hello,
This crash occurred once logged in.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Mar 25 16:51:29 2018
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2018-03-24 (1 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180324)
JournalErrors:
 -- Logs begin at Sat 2018-03-24 16:57:46 CET, end at Sun 2018-03-25 18:07:13 CEST. --
 mars 25 18:05:42 hostname kernel: Spectre V2 : Spectre mitigation: LFENCE not serializing, switching to generic retpoline
 mars 25 18:05:46 hostname spice-vdagent[880]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 mars 25 18:05:57 hostname spice-vdagent[1298]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
 mars 25 18:06:10 hostname pulseaudio[1181]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ProcCmdline: /usr/bin/gnome-shell
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in g_log_default_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[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.