[systemd-devel] Logind error - Failed to abandon session scope: Connection reset
roger.qiu at polycademy.com
Sat Aug 16 21:48:36 PDT 2014
The reason why you don't want explicit ordering is because of a slower
When you are referring to patching them out, would that be from upstream
On 15/08/2014 7:41 PM, Lennart Poettering wrote:
> On Fri, 15.08.14 15:04, Roger Qiu (roger.qiu at polycademy.com) wrote:
>> Hello Lennart,
>> Thanks for answering.
>> Is there any way to enforce ordering to make this error not occur?
> You could order systemd-logind.service After= dbus.service. That way
> dbus is started first, and logind second. And since the top order is the
> reversed start order, this would result in logind being stopped first
> and dbus second.
> But honestly, I don't really like this, we should no add unnecessary
> ordering here...
>> Or what's the best way to hide that warning?
> We should probably just patch it out...
>> Or when is the ETA for kdbus?
> Well, "when it's ready"...
More information about the systemd-devel