lightdm crashed with SIGABRT in _g_log_abort()

Bug #1231841 reported by Giuseppe Fierro on 2013-09-27
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Light Display Manager
Critical
Robert Ancell
1.8
Critical
Robert Ancell
1.9
Critical
Robert Ancell
lightdm (Ubuntu)
Critical
Robert Ancell

Bug Description

Lightdm continue to crash on my two systems. Ati and Nvidia.
Usually every 2 or 3 boot lightdm doesn't start.
This is very very annoying please fix this issue.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: lightdm 1.7.17-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1
Uname: Linux 3.11.0-8-generic x86_64
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
Date: Thu Sep 26 22:20:20 2013
ExecutablePath: /usr/sbin/lightdm
InstallationDate: Installed on 2013-09-22 (4 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130905)
MarkForUpload: True
ProcCmdline: lightdm restart
Signal: 6
SourcePackage: lightdm
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_filename_display_name () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: lightdm crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Related branches

Giuseppe Fierro (gspe) wrote :
Changed in lightdm (Ubuntu):
importance: Undecided → Medium
summary: - lightdm crashed with SIGABRT in g_assertion_message()
+ lightdm crashed with SIGABRT in _g_log_abort()
tags: removed: need-amd64-retrace
information type: Private → Public
Changed in lightdm (Ubuntu):
status: New → In Progress
importance: Medium → High
assignee: nobody → Robert Ancell (robert-ancell)
importance: High → Critical
Changed in lightdm:
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Robert Ancell (robert-ancell)
Robert Ancell (robert-ancell) wrote :

I suspect this is not hitting most people since they won't have any lock files when starting lightdm (no other X servers around).

PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:lightdm at revision 1816, scheduled for release in lightdm, milestone Unknown

Changed in lightdm:
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lightdm - 1.8.2-0ubuntu1

---------------
lightdm (1.8.2-0ubuntu1) saucy; urgency=low

  * New upstream release:
    - Fix crash when starting with existing X servers. This was introduced in
      rev 1651 (lightdm 1.7.0). (LP: #1231841)
 -- Robert Ancell <email address hidden> Wed, 16 Oct 2013 15:46:40 +1300

Changed in lightdm (Ubuntu):
status: In Progress → Fix Released
Giuseppe Fierro (gspe) wrote :

This bug is still present with lightdm 1.8.2-0ubuntu1

Giuseppe Fierro (gspe) wrote :
Giuseppe Fierro (gspe) wrote :
Changed in lightdm:
status: Fix Committed → Fix Released
status: Fix Released → New
Robert Ancell (robert-ancell) wrote :

Giuseppe - your logs show no problem - please file a new bug when you get a crash report as that will show if you are having the same problem.

Changed in lightdm:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers