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