7100 2014-12-23 10:31:11 +0000 systemd startup fails due to timeout 2015-01-26 09:08:50 +0000 1 1 11 Runtime General Runtime General Runtime 1.8 x86 Multiple RESOLVED FIXED Medium+ normal 1.8 M2 1 bluelightning randy.e.witt alexandru.c.georgescu ross.burton georgex.l.musat --- --- No (bug/feature does not impact docs) oldest_to_newest 47658 0 bluelightning 2014-12-23 10:31:11 +0000 The test_parselogs QA test on the autobuilder for nightly_qa_systemd (qemux86-64) failed: (EE) systemd-logind: failed to get session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Full log: https://autobuilder.yoctoproject.org/main/builders/nightly-qa-systemd/builds/135/steps/Running%20Sanity%20Tests/logs/stdio (This was for master-next, but the same issue will be present on master.) 48164 1 randy.e.witt 2015-01-21 23:11:48 +0000 We solved this for now by disabling systemd-logind for X unconditionally. In the future we can reinvestigate with things we learned this time. Notes: Sessions must be registered with systemd-logind via pam. This means pam must be enabled for systemd-logind to work properly. Usually the dm is responsible for creating new sessions for the available seats and then starting a process for each available seat. If starting a process that creates a session via pam, you can specify items such as the seat and vt number to pam using the variables at http://www.freedesktop.org/software/systemd/man/pam_systemd.html#Environment. Even when specifying the seat and vt to pam, in order for the session to work properly, the seat also had to be passed to the Xserver as the last argument on the command line in a form such as "/etc/X11/Xserver vt1".