lightm/upstart crash leaves 2 unity8 processes around

Bug #1385444 reported by Daniel Holbach
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lightdm (Ubuntu)
New
Undecided
Unassigned
upstart (Ubuntu)
New
Undecided
Unassigned

Bug Description

lightm/upstart crash leaves 2 unity8 processes around

Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

(None of the crash files were related to the bug.)

Revision history for this message
James Hunt (jamesodhunt) wrote :

The oldest of the two unity8 proceses (pid 2640) has been SIGSTOP'ed. Since unity8 uses SIGSTOP to indicate to upstart that it is ready, this suggests that when lightdm died, the session init was killed somehow before unity8 was ready (either on first start or respawn).

Revision history for this message
James Hunt (jamesodhunt) wrote :

Daniel - please can you attach the existing /var/crash/_sbin_init* to this bug. I appreciate they do not represent the current issue, but if may have been a re-occurence of the problem which did generated the crash files so I'd like to see those anyway.

Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

This is still happening to me.

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.