touch-packages team mailing list archive

[Ryan Tandy <1410584@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Dear maintainer,

When lightdm is stopped or restarted, unity-greeter does not get a
chance to run its cleanup code, but simply aborts due to the X server
going away. Most of the greeter session components die the same way, but
the session upstart does not. It keeps running and attempting to respawn
services, which results in these few processes and the logind session
staying around.

I'm not sure whether this bug belongs properly to lightdm or unity-
greeter. It's possible the greeter should react more gracefully when the
X server vanishes. I'm filing this against lightdm right now because I
feel like all the necessary code for this already exists, it just needs
to be called in the right order at the right time. Maybe it just needs
to wait for the sessions attached to a particular display server to
finish before stopping that server.

Thanks.

** Affects: lightdm (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1410584

Title:
  please stop greeter gracefully when stopping lightdm

Status in lightdm package in Ubuntu:
  New

Bug description:
  Dear maintainer,

  When lightdm is stopped or restarted, unity-greeter does not get a
  chance to run its cleanup code, but simply aborts due to the X server
  going away. Most of the greeter session components die the same way,
  but the session upstart does not. It keeps running and attempting to
  respawn services, which results in these few processes and the logind
  session staying around.

  I'm not sure whether this bug belongs properly to lightdm or unity-
  greeter. It's possible the greeter should react more gracefully when
  the X server vanishes. I'm filing this against lightdm right now
  because I feel like all the necessary code for this already exists, it
  just needs to be called in the right order at the right time. Maybe it
  just needs to wait for the sessions attached to a particular display
  server to finish before stopping that server.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1410584/+subscriptions