← Back to team overview

desktop-packages team mailing list archive

[Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed


> Can you see if this solves the issue on your computers?

No luck here (Xubuntu 14.04), what actually did fix the issue was
installing the latest stable release of lightdm-gtk-indicator from the
upstream ppa. This caused a few hiccups with the Greybird theme, but at
least the ghost sessions are gone without any kind of workaround.

This is a glaring red sign that neither lightdm nor upstart are the
appropriate packages for this issue, but lightdm-gtk-greeter is.

Anyone proficient with bzr willing to perform a bisect between 2.0.1
(ppa - working) and 1.8.5 (trusty-updates, not working)?

** Also affects: lightdm-gtk-greeter (Ubuntu)
   Importance: Undecided
       Status: New

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.

  lightdm sessions started by dm-tool lock (or a session locker) never
  get closed

Status in Light Display Manager:
Status in lightdm package in Ubuntu:
Status in lightdm-gtk-greeter package in Ubuntu:
Status in upstart package in Ubuntu:

Bug description:
  dm-tool lock starts a new lightdm greeter (for unlocking) and a new
  logind session. After unlocking the greeter disappears, but the logind
  session never closes. loginctl session status c24 reports something

  c24 - lightdm (103)
             Since: Thu 2014-05-22 18:38:27 CEST; 30min ago
            Leader: 7872
              Seat: seat0; vc8
           Display: :1
           Service: lightdm-greeter; type x11; class greeter
             State: closing
            CGroup: systemd:/user/103.user/c24.session
                    └─7907 init --user --startup-event indicator-services-start

  This results in an accumulation of stale lightdm sessions after using
  e.g. a session locker for a while.

  I get this issue on a freshly installed and fully updated Xubuntu

To manage notifications about this bug go to:

Follow ups