lightdm crashed with SIGSEGV in g_closure_invoke()

Bug #819314 reported by Alexandre Otto Strube
100
This bug affects 18 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Fix Released
Undecided
Michael Terry
lightdm (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Perhaps a dupe of #809890 , but LP doesn't allow me to - just sending the reports with full update at aug 1st, 2011.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: lightdm 0.9.2-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Aug 1 15:33:24 2011
ExecutablePath: /usr/sbin/lightdm
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
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 () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: lightdm crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to oneiric on 2011-07-27 (5 days ago)
UserGroups:

Related branches

Revision history for this message
Alexandre Otto Strube (surak) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 xsession_start (session=0x9b29e0) at xsession.c:80
 start_user_session (display=0x9868c0) at display.c:848
 greeter_session_stopped_cb (session=<value optimized out>, display=0x9868c0) at display.c:556
 greeter_session_stopped_cb (session=<value optimized out>, display=0x9868c0) at display.c:532
 g_closure_invoke (closure=0x9b19b0, return_value=0x0, n_param_values=1, param_values=0x9b8fa0, invocation_hint=<value optimized out>) at /build/buildd/glib2.0-2.29.14/./gobject/gclosure.c:773

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in lightdm (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in lightdm (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in lightdm (Ubuntu):
importance: Medium → High
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 After this poup system still running without problems

Changed in lightdm:
status: New → Confirmed
Changed in lightdm (Ubuntu):
status: Confirmed → Triaged
Michael Terry (mterry)
Changed in lightdm:
assignee: nobody → Michael Terry (mterry)
status: Confirmed → In Progress
Revision history for this message
stop (whoopwhoop) wrote :

Guys, do you find lightdm using 100% cpu after you log in? Lightdm uses 100% cpu for me all the time.

Michael Terry (mterry)
Changed in lightdm:
status: In Progress → Fix Released
Changed in lightdm (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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