Quirky session behavior w/ systemd from ppa:pitti/systemd

Attaching the output of journalctl as requested.

Attaching journalctl w/ kernel debug.

Jul 07 09:28:32 Slave1 gnome-session[1850]: gnome-session[1850]: WARNING: Shutdown failed: GDBus.Error:org.freedesktop.DBus.Error.InteractiveAuthorizationRequired: Interactive authentication required.

This is probably because this is all mixed up:

        c1 110 lightdm seat0
         1 1000 townsend

That means lightdm has the "foreground" session, and your XDG_SESSION_ID is c1. And "your" session is a remote one "1".

This is very likely http://lists.freedesktop.org/archives/systemd-devel/2015-July/033464.html

When you are in that situation, can you please attach the output of "systemd-cgls" so that we know why the lightdm greeter session doesn't terminate properly? I. e. which process is keeping it from shutting down?

The requested systemd-cgls output.

Hey Martin,

I see on that systemd-devel thread that a potential fix has been committed. If you update your PPA, I will try it an see if it fixes it for me.

Thanks for looking at this!

Thanks for confirming! So this is definitively from leftovers of the lightdm session:

  └─user-110.slice
    ├─user@110.service
    │ ├─996 /lib/systemd/systemd --user
    │ └─997 (sd-pam)
    └─session-c1.scope
      ├─1149 /usr/bin/pulseaudio --start --log-target=syslog
      └─1168 /usr/lib/pulseaudio/pulse/gconf-helper

Right after logging in I also could briefly reproduce this, I had

        c2 1000 martin seat0
        c1 115 lightdm seat0

but unfortunately it didn't last long enough to get "loginctl session-status c1", I suppose the leaked processes eventually just timed out. But this would be enough to cause this.

Building updated PPA package now, will take some 45 mins to get through all the tests.

Christopher: systemd 221+upstream20150707-0.ubuntu1 uploaded to PPA, will be built in pretty much exactly one hour.

Hey Martin,

Yes, the updated package in your PPA fixes the issue in this bug. I also confirmed that unprivileged LXC's still start.

Thanks again!

Thanks for verifying! As this only affected the PPA I'm closing this now.