lightdm crashed with SIGSEGV in child_process_signal()

Bug #806021 reported by C de-Avillez
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned

Bug Description

Logged out and in again. Nothing unique.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: lightdm 0.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic x86_64
NonfreeKernelModules: wl nvidia
Architecture: amd64
Date: Tue Jul 5 10:41:15 2011
ExecutablePath: /usr/bin/lightdm
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110228)
ProcCmdline: lightdm
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x406b20 <child_process_signal+32>: mov 0x2c(%rax),%r8d
 PC (0x00406b20) ok
 source "0x2c(%rax)" (0xaaaaaaaaaaaaaad6) not located in a known VMA region (needed readable region)!
 destination "%r8d" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 child_process_signal (process=0x1633ae0, signum=15) at child-process.c:357
 quit_greeter_cb (data=0x1633ae0) at greeter.c:394
 g_timeout_dispatch (source=0x7f649c00e920, callback=<value optimized out>, user_data=<value optimized out>) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:3955
 g_main_dispatch (context=0x162dd20) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:2477
 g_main_context_dispatch (context=0x162dd20) at /build/buildd/glib2.0-2.29.8/./glib/gmain.c:3050
Title: lightdm crashed with SIGSEGV in child_process_signal()
UpgradeStatus: Upgraded to oneiric on 2011-06-27 (8 days ago)
UserGroups:

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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #798716, 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.

visibility: private → public
tags: removed: need-amd64-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.