[arch-general] at times when booting system-logind fails and system hangs

[Mark Lee]

On Wednesday, April 29, 2015 07:17:53 PM Javier Vasquez wrote:
> > On Wed, Apr 29, 2015 at 3:51 PM, Mark Lee <mark at markelee.com> wrote:
> > ...
> > Systemd usually logs startup in journalctl. Can you post your journalctl
> > output (from a time when you're sure you had the issue)?
> 
> Not sure how useful it is.  Not sure if attaching the whole output,
> but here it goes what related to logind:
> 
> ++++++++++
> Apr 29 15:11:22 m1 systemd[1]: Starting Login Service...
> ...
> Apr 29 15:11:52 m1 systemd[1]: Unit systemd-logind.service entered failed
> state. Apr 29 15:11:52 m1 systemd[1]: systemd-logind.service failed.
> Apr 29 15:11:52 m1 systemd[1]: systemd-logind.service has no holdoff
> time, scheduling restart.
> Apr 29 15:11:23 m1 systemd[1]: Starting Permit User Sessions...
> Apr 29 15:11:23 m1 systemd[1]: Started D-Bus System Message Bus.
> Apr 29 15:11:52 m1 systemd-logind[383]: Failed to enable subscription:
> Connection timed out
> Apr 29 15:11:52 m1 systemd-logind[383]: Failed to fully start up
> daemon: Connection timed out

Can you post the output of your /etc/logind.conf?

Regards,
Mark
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20150429/142c3b18/attachment.asc>