ubuntu-x-swat team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

This appears to be caused by the xdm package not integrating with
upstart.  The plymouth process which holds the console open is waiting
for a signal that the xdm job is starting up, so that it can let go of
the console; but the xdm package, which is not well cared for in Ubuntu,
doesn't have an upstart job, so there's no signal sent, which means the
plymouth and xdm processes are fighting over the console.

Marking bug #723698 as a duplicate of this one.  This is unfixed in
natty, maverick and lucid.

** Project changed: slim => lqueue

** Also affects: xdm (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Also affects: xdm (Ubuntu Maverick)
   Importance: Undecided
       Status: New

** Also affects: xdm (Ubuntu Natty)
   Importance: High
       Status: Triaged

** Changed in: xdm (Ubuntu Maverick)
       Status: New => Triaged

** Changed in: xdm (Ubuntu Lucid)
       Status: New => Triaged

** Changed in: xdm (Ubuntu Lucid)
   Importance: Undecided => High

** Changed in: xdm (Ubuntu Maverick)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdm in ubuntu.
https://bugs.launchpad.net/bugs/585853

Title:
  Not possible to use xdm/wdm, only can use gdm (Lucid, Maverick)