lightdm crashed with SIGSEGV in g_closure_invoke()

Bug #816980 reported by Ted Gould
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Wasn't able to login with lightdm today.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: lightdm 0.9.2-0ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Tue Jul 26 20:03:46 2011
ExecutablePath: /usr/sbin/lightdm
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: lightdm
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x416de1: mov 0x8(%rax),%rcx
 PC (0x00416de1) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: lightdm
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke (closure=0x221ca20, return_value=0x0, n_param_values=1, param_values=0x2220c20, invocation_hint=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./gobject/gclosure.c:773
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x221c040, emission_return=0x0, instance_and_params=0x2220c20) at /build/buildd/glib2.0-2.29.14/./gobject/gsignal.c:3271
Title: lightdm crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-06-17 (39 days ago)
UserGroups:

mtime.conffile..etc.lightdm.lightdm.conf: 2011-07-14T08:32:58.709134

Revision history for this message
Ted Gould (ted) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 g_closure_invoke (closure=0x221ca20, return_value=0x0, n_param_values=1, param_values=0x2220c20, invocation_hint=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./gobject/gclosure.c:773
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x221c040, emission_return=0x0, instance_and_params=0x2220c20) at /build/buildd/glib2.0-2.29.14/./gobject/gsignal.c:3271

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Hernando Torque (htorque) wrote :

Getting the same crash. The greeter starts, then after logging in it's just a pointer and nothing happens.

Changed in lightdm (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexandre Otto Strube (surak) wrote :

I hate the "mee toos", but... me too :)

Revision history for this message
katmen (katmen) wrote :

today freshly installed oneiric alpha 2 after first boot lightgdm failed to start, i cant login via it, it seems that theme is also broken eg it is has win95 look

tags: added: need-amd64-retrace
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 #819314, 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.

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.