gnome-shell crashed with SIGSEGV in g_closure_invoke()

[AlfonSkunk]

$ lsb_release -rd
Description: Ubuntu Artful Aardvark (development branch)
Release: 17.10

$ apt-cache policy gnome-shell
gnome-shell:
  Instalados: 3.25.91-0ubuntu3
  Candidato: 3.25.91-0ubuntu3
  Tabla de versión:
 *** 3.25.91-0ubuntu3 500
        500 http://es.archive.ubuntu.com/ubuntu artful/main amd64 Packages
        100 /var/lib/dpkg/status

Everything works ok after the crash, but the failure appears on every login.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.25.91-0ubuntu3
ProcVersionSignature: Ubuntu 4.11.0-13.19-generic 4.11.12
Uname: Linux 4.11.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Sep 5 08:57:08 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2017-07-19 (47 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7f93e7472836: mov 0x1a0(%rax),%rax
 PC (0x7f93e7472836) ok
 source "0x1a0(%rax)" (0x000001a0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 drmHandleEvent () from /usr/lib/x86_64-linux-gnu/libdrm.so.2
 meta_monitor_manager_kms_wait_for_flip () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGSEGV in g_closure_invoke()
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 #1714330, 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.