lightdm crashed with SIGSEGV in check_stopped()

Bug #902698 reported by Macron
150
This bug affects 20 people
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
Fix Released
High
Unassigned
Precise
Fix Released
High
Unassigned

Bug Description

Bug last reported on 2011/9/14 with "Fix Released" stated but seems to have happened again in 12.04 alpha

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: lightdm 1.0.6-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Sun Dec 11 11:25:45 2011
ExecutablePath: /usr/sbin/lightdm
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: lightdm
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x411138: mov 0x28(%rax),%ecx
 PC (0x00411138) ok
 source "0x28(%rax)" (0xaaaaaaaaaaaaaad2) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown 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
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: lightdm crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to precise on 2011-12-04 (6 days ago)
UserGroups:

Related branches

Revision history for this message
Macron (macronsfx) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 check_stopped (seat=0xf51a40) at seat.c:415
 g_closure_invoke (closure=0xf5f0f0, return_value=0x0, n_param_values=1, param_values=0xf62740, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.2/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0xf62740) at /build/buildd/glib2.0-2.31.2/./gobject/gsignal.c:3302
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fff3bf83938) at /build/buildd/glib2.0-2.31.2/./gobject/gsignal.c:3033
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.31.2/./gobject/gsignal.c:3090

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
summary: - lightdm crashed with SIGSEGV in g_closure_invoke()
+ lightdm crashed with SIGSEGV in check_stopped()
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lightdm (Ubuntu):
status: New → Confirmed
visibility: private → public
Changed in lightdm (Ubuntu):
assignee: nobody → Robert Ancell (robert-ancell)
importance: Medium → High
Changed in lightdm (Ubuntu Precise):
status: Confirmed → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

Robert, I'm reopening this bug since we got duplicates using lightdm 1.1.1 which was rolled after your fix and should have fixed the issue

Changed in lightdm (Ubuntu Precise):
status: Fix Committed → Triaged
tags: added: rls-mgr-p-tracking
Revision history for this message
J Cord (j7cord) wrote : Re: [Bug 902698] Re: lightdm crashed with SIGSEGV in check_stopped()

I am not getting this bug to happen now, I have switched to my computer
which uses Intel 3000 graphics, where the one I reported the crash on is an
earlier I7 without the 3000 series graphics and with a AMD ATi 6700 series
gdm. I was having no end of crashes after recent update on that machine.
 Actually so bad I thought I had a bad hard drive and replaced it, still
the same. The computer itself runs Fedora and Suse fine. Which leads me
to believe it is a problem between the gdm and precise. CPU nor gdm is
overclocked and using xorg drivers. Hope that may help.
Thank You

On Tue, Dec 20, 2011 at 11:13 PM, Launchpad Bug Tracker <
<email address hidden>> wrote:

> ** Branch linked: lp:lightdm
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (905405).
> https://bugs.launchpad.net/bugs/902698
>
> Title:
> lightdm crashed with SIGSEGV in check_stopped()
>
> Status in “lightdm” package in Ubuntu:
> Fix Committed
> Status in “lightdm” source package in Precise:
> Fix Committed
>
> Bug description:
> Bug last reported on 2011/9/14 with "Fix Released" stated but seems to
> have happened again in 12.04 alpha
>
> ProblemType: Crash
> DistroRelease: Ubuntu 12.04
> Package: lightdm 1.0.6-0ubuntu4
> ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
> Uname: Linux 3.2.0-3-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 1.90-0ubuntu1
> Architecture: amd64
> CrashCounter: 1
> Date: Sun Dec 11 11:25:45 2011
> ExecutablePath: /usr/sbin/lightdm
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64
> (20111012)
> ProcCmdline: lightdm
> ProcEnviron: PATH=(custom, no user)
> SegvAnalysis:
> Segfault happened at: 0x411138: mov 0x28(%rax),%ecx
> PC (0x00411138) ok
> source "0x28(%rax)" (0xaaaaaaaaaaaaaad2) not located in a known VMA
> region (needed readable region)!
> destination "%ecx" ok
> SegvReason: reading unknown 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
> g_signal_emit_valist () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: lightdm crashed with SIGSEGV in g_closure_invoke()
> UpgradeStatus: Upgraded to precise on 2011-12-04 (6 days ago)
> UserGroups:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/902698/+subscriptions
>

tags: added: rls-p-tracking
tags: removed: rls-p-tracking
Revision history for this message
Rich Hart (sirwizkid) wrote :

Both this and GDM are crashing on my system. It started after I tried the latest graphic driver #876499. I have X working again, but neither graphic login package will run.

Revision history for this message
Robert Ancell (robert-ancell) wrote :

Closing assumed fixed.

Changed in lightdm (Ubuntu):
status: Triaged → Fix Released
Changed in lightdm (Ubuntu Precise):
status: Triaged → Fix Released
Changed in lightdm (Ubuntu):
assignee: Robert Ancell (robert-ancell) → nobody
Changed in lightdm (Ubuntu Precise):
assignee: Robert Ancell (robert-ancell) → nobody
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.