Hide Forgot
Description of problem: Mar 16 05:37:54 localhost systemd[1]: Starting Login Service... Mar 16 05:37:56 localhost systemd[1]: Starting Initial Setup configuration program... Mar 16 05:38:00 localhost systemd[1]: Started D-Bus System Message Bus. Mar 16 05:38:12 localhost dbus[1030]: [system] Successfully activated service 'org.freedesktop.systemd1' Mar 16 05:38:13 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit= Mar 16 05:38:14 localhost systemd[1]: Starting firewalld - dynamic firewall daemon... Mar 16 05:38:17 localhost systemd[1]: Starting NTP client/server... Mar 16 05:38:19 localhost systemd[1]: Starting Permit User Sessions... Mar 16 05:38:21 localhost systemd[1]: Received SIGRTMIN+21 from PID 1026 (kill). Mar 16 05:38:24 localhost chronyd[1049]: chronyd version 2.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SECHASH +ASYNCDN Mar 16 05:38:32 localhost systemd[1]: Received SIGRTMIN+21 from PID 998 (plymouthd). Mar 16 05:38:34 localhost audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=p Mar 16 05:38:36 localhost systemd-logind[1022]: Failed to enable subscription: Connection timed out Mar 16 05:38:39 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit= Mar 16 05:38:37 localhost systemd-logind[1022]: Failed to fully start up daemon: Connection timed out Mar 16 05:38:39 localhost systemd[1]: Started Permit User Sessions. Mar 16 05:38:43 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit= Mar 16 05:38:40 localhost systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE Mar 16 05:38:43 localhost systemd[1]: Failed to start Login Service. Mar 16 05:38:43 localhost systemd[1]: systemd-logind.service: Unit entered failed state. Mar 16 05:38:43 localhost systemd[1]: systemd-logind.service: Failed with result 'exit-code'. Mar 16 05:38:52 localhost systemd[1]: Cannot find unit for notify message of PID 1022. Mar 16 05:38:54 localhost audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit= Mar 16 05:38:53 localhost systemd[1]: Started NTP client/server. Mar 16 05:38:57 localhost systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Version-Release number of selected component (if applicable): systemd-229-6.fc24.armv7hl How reproducible: Always Steps to Reproduce: 1. Boot minimal arm image 2. wait Actual results: Both initial-setup and logind fail to start Expected results: initial-setup-tui and happiness.
Also, received on the console: Cannot open access to console, the root account is locked. Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
Proposed as a Blocker for 24-alpha by Fedora user jdulaney using the blocker tracking app because: Proposing under the criteria: Release-blocking ARM disk images must boot to the initial-setup utility.
Looks like some dbus issue... Could you investigate what happens when you restart systemd-logind.service by hand? Is dbus otherwise functional?
Paul, have you seen this? John, what image did you boot exactly? What ARM system did you boot it on?
(In reply to Adam Williamson from comment #4) > Paul, have you seen this? > > John, what image did you boot exactly? What ARM system did you boot it on? I haven't. I confirmed its working here on the Beaglebone Black and qemu in Alpha 1.1.
I just redownloaded and was unable to reproduce. Might be I got a bad image. Closing accordingly.