unity-greeter crashed with SIGSEGV in lightdm_layout_get_description()

Bug #1206087 reported by Andy Whitcroft
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-greeter (Ubuntu)
New
Undecided
Unassigned

Bug Description

crashed on boot

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-greeter 13.10.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2
Uname: Linux 3.10.0-5-generic i686
ApportVersion: 2.11-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Jul 29 11:23:24 2013
ExecutablePath: /usr/sbin/unity-greeter
InstallationDate: Installed on 2010-05-06 (1179 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MarkForUpload: True
ProcCmdline: /usr/sbin/unity-greeter
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0xb6ddfe33 <lightdm_layout_get_description+35>: cmp %eax,(%edx)
 PC (0xb6ddfe33) ok
 source "%eax" ok
 destination "(%edx)" (0x00000001) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: unity-greeter
StacktraceTop:
 lightdm_layout_get_description () from /usr/lib/liblightdm-gobject-1.so.0
 ?? ()
 g_list_sort_merge (user_data=0x0, compare_func=0x8064640, l2=0x8856740, l1=0x8856600) at /build/buildd/glib2.0-2.37.3/./glib/glist.c:1066
 g_list_sort_real (list=<optimised out>, compare_func=0x8064640, user_data=0x0) at /build/buildd/glib2.0-2.37.3/./glib/glist.c:1112
 ?? ()
Title: unity-greeter crashed with SIGSEGV in lightdm_layout_get_description()
UpgradeStatus: Upgraded to saucy on 2013-06-05 (53 days ago)
UserGroups:

Revision history for this message
Andy Whitcroft (apw) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #1196915, 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.

information type: Private → Public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.