On 15/10/2017 11:08, Arve Barsnes wrote: > > > On 15 October 2017 at 10:32, Alan McKinnon <alan.mckin...@gmail.com > <mailto:alan.mckin...@gmail.com>> wrote: > > On 14/10/2017 11:55, Arve Barsnes wrote: > > On 14 October 2017 at 08:37, Alan McKinnon <alan.mckin...@gmail.com > <mailto:alan.mckin...@gmail.com> > > <mailto:alan.mckin...@gmail.com <mailto:alan.mckin...@gmail.com>>> > wrote: > > > > A quick heads-up to anyone who like me uses sddm on a plain openrc > box > > with USE="-elogind -systemd" and upgrades to sddm-0.16.0 (recently > > released) > > > > That combination does not work. The xdm service starts, sddm > launches, > > logs a message that doesn't look too ominous and then does ... > nothing. > > No sddm, No X-Server. Very confusing, took me a while to solve. > > > > > > That's interesting. This combination works just fine here. Installed > > 0.16.0 Wednesday, rebooted Thursday, sddm worked as normal. > > USE="consolekit pam -elogind -systemd" > > The gentoo bug shows that the problem is a function defined in elogind > that should also be in consolekit but isn't. So obviously there's > something additional going on. > > Your USE for sddm is "-elogind" true enough, do you maybe have elgind > installed anyway for some other reason? > > No, I do not. I agree that something must be providing this function on > my system though. We all have consolekit-1.2.0 I assume?
Yes, that is the consolekit I have too. I can't check any of this right now but I recall in the gentoo bug and referenced sddm bug lots of talk of Seats etc. And there's a sddm module for pam too. The difference might be in there. Meanwhile Michael has pushed an -r1 workaround that needs testing -- Alan McKinnon alan.mckin...@gmail.com
