unity-greeter crashed with SIGSEGV in lightdm_layout_get_description()

[Benjamin Drung]

Apport showed the crash report after logging in.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-1.8-generic 3.10.0-rc7
Uname: Linux 3.10.0-1-generic x86_64
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Tue Jul 2 13:12:03 2013
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2012-06-05 (391 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f0eeeedf926 <lightdm_layout_get_description+22>: cmp %rax,(%rdx)
 PC (0x7f0eeeedf926) ok
 source "%rax" ok
 destination "(%rdx)" (0xaaaaaaaaaaaaaaaa) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 lightdm_layout_get_description () from /usr/lib/liblightdm-gobject-1.so.0
 ?? ()
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: unity-greeter crashed with SIGSEGV in lightdm_layout_get_description()
UpgradeStatus: Upgraded to saucy on 2013-06-03 (28 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 lightdm_layout_get_description (layout=0x1d3fc60) at layout.c:241
 menu_bar_cmp_layout (b=0x1d3dea0, a=<optimized out>) at menubar.c:1075
 _menu_bar_cmp_layout_gcompare_func (a=<optimized out>, b=0x1d3dea0) at menubar.c:1593
 g_list_sort_merge (user_data=0x0, compare_func=0x41ddd0 <_menu_bar_cmp_layout_gcompare_func>, l2=0x1a42000, l1=0x1a8eb80) at /build/buildd/glib2.0-2.37.3/./glib/glist.c:1066
 g_list_sort_real (list=<optimized out>, compare_func=compare_func@entry=0x41ddd0 <_menu_bar_cmp_layout_gcompare_func>, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.37.3/./glib/glist.c:1112

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anthony Granger (chocanto)]

This error appear right after logging in on Ubuntu 13.10