On dim., 2014-05-25 at 18:28 +0200, Yves-Alexis Perez wrote: > On dim., 2014-05-25 at 17:58 +0200, Thomas Bartscher wrote: > > None of these problems appear when lightdm is started automatically at > > boot time. > > My guess is that it's because you don't have a consolekit session > properly set up when manually starting lightdm. > > You might want to try starting lightdm as root (directly, not using > sudo), but in any case there's not much we can do here.
I experienced the same issue on a sid box, and what worked for me was to install (in that order): - systemd-shim - libpam-systemd I think policykit was switched to logind (so consolekit is not useful anymore). I think you need to install them in that specific order because systemd-shim will fulfill dependencies needed for libpam-systemd (which would otherwise pull systemd-as-init stuff, which might not be what you want right now). Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
