gdm crashed with SIGSEGV

[Andreas Brauchli]

Not quite sure if this is the report for the X (or gdm) crash when gdm restarted when I exited weston.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gdm 3.14.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
Uname: Linux 3.18.0-13-generic x86_64
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
Date: Sat Feb 21 21:57:52 2015
ExecutablePath: /usr/sbin/gdm
InstallationDate: Installed on 2013-07-22 (579 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 (20130626)
ProcCmdline: gdm
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x411b50: mov 0x18(%rdi),%rax
 PC (0x00411b50) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gdm
StacktraceTop:
 ()
 ()
 g_main_context_dispatch (context=0xd3f950) at /build/buildd/glib2.0-2.43.4/./glib/gmain.c:3122
 g_main_context_dispatch (context=context@entry=0xd3f950) at /build/buildd/glib2.0-2.43.4/./glib/gmain.c:3737
 g_main_context_iterate (context=0xd3f950, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.43.4/./glib/gmain.c:3808
Title: gdm crashed with SIGSEGV
UpgradeStatus: Upgraded to vivid on 2015-01-24 (28 days ago)
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 #1419324, 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.