lightdm crashed with SIGSEGV in g_signal_emit_valist()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lightdm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This must have happened when starting the machine. The only thing I noticed is that it took longer than normal to get to the gui login prompt.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: lightdm 1.4.0-0ubuntu3
ProcVersionSign
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Thu Feb 14 08:13:41 2013
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2012-11-09 (97 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
LightdmConfig:
[SeatDefaults]
user-session=
greeter-
MarkForUpload: True
ProcCmdline: lightdm
ProcEnviron:
TERM=linux
PATH=(custom, no user)
SegvAnalysis:
Segfault happened at: 0x410518: mov 0x28(%rax),%ecx
PC (0x00410518) ok
source "0x28(%rax)" (0xaaaaaaaaaaaa
destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
?? ()
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/
?? () from /usr/lib/
Title: lightdm crashed with SIGSEGV in g_signal_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
mtime.conffile.
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 #1127251, 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.