[systemd-devel] [HEADS-UP] PID 1 now ported to libsystemd-bus

[Tom Gundersen]

On Fri, Nov 22, 2013 at 2:33 PM, Lennart Poettering
<lennart at poettering.net> wrote:
> On Thu, 21.11.13 10:03, Oleksii Shevchuk (alxchk at gmail.com) wrote:
>
>>
>> Segfaults fixed, but:
>>
>> systemd-logind[2167]: Failed to start session scope session-3.scope: Invalid arguments 'ssa(sv)' to call org.freedesktop.systemd1.Manager:StartTransientUnit, expecting 'ssa(sv)a(sa(sv))'. org.freedesktop.DBus.Error.InvalidArgs
>> lightdm[2594]: pam_systemd(lightdm:session): Failed to create session: Invalid argument
>> lightdm[2168]: ** (process:2594): WARNING **: Failed to open login1 session: GDBus.Error:org.freedesktop.login1.NoSessionForPID: PID 2594 does not belong to any known session
>
> That should be fixed now.

It now boots for me, or most things seem to work as they should. There
seems to be a few issues left though.

For instance "systemd-analyze critical-chain" gives:

# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @909ms

Whereas "systemd-analyze" gives:

Startup finished in 3.091s (firmware) + 12ms (loader) + 3.773s
(kernel) + 158ms (initrd) + 574ms (userspace) = 7.610s

So something is obviously missing from the critical chain, and the
timings given to (userspace) seem to be too low...

-t