You are not logged in.
The boot sequence had a logind.service fail, and then was stuck when trying to open the Gnome Display Manager. The output was:
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
[ OK ] Started dhcpd on enp4s0.
[ OK ] Reached target Network.
Starting Network Time Service...
[ OK ] Started Network Time Service.
[ OK ] Reached target Multi-User System.
[FAILED] Failed to start GNOME Display Manager.
See "systemctl status gdm.service" for details.
[ OK ] Reached target Graphical Interface.
_
I have disabled the gdm.service using an installation disk with chroot in order to login, and after the restart I tried `sudo systemctl status systemd-logind.service`. The output is:
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
Active: failed (Result: start-limit) since 月 2015-04-06 17:59:52 JST; 56s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 249 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 249 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
4月 06 17:59:52 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 06 17:59:52 masasin-arch systemd[1]: Stopping Login Service...
4月 06 17:59:52 masasin-arch systemd[1]: Starting Login Service...
4月 06 17:59:52 masasin-arch systemd[1]: start request repeated too quickly for systemd-logind.service
4月 06 17:59:52 masasin-arch systemd[1]: Failed to start Login Service.
4月 06 17:59:52 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 06 17:59:52 masasin-arch systemd[1]: systemd-logind.service failed.
At the moment, I cannot get into any graphical environments, but I do have access to the shell.
Let me know if you need more information.
Offline
I ran
journalctl -b -u systemd-logind
right after a reboot, and the output is as follows:
-- Logs begin at 水 2013-08-21 08:01:49 JST, end at 水 2015-04-08 18:26:45 JST. --
4月 08 18:26:14 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:14 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:14 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:14 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:14 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:14 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:14 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:14 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: start request repeated too quickly for systemd-logind.service
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
Offline
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
This suggests a problem with D-Bus. Any other errors in the journal?
Offline
masasin wrote:4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
This suggests a problem with D-Bus. Any other errors in the journal?
journalctl -b -u dbus
gives:
-- Logs begin at 水 2013-08-21 08:01:49 JST, end at 水 2015-04-08 19:20:15 JST. --
4月 08 18:26:14 masasin-arch systemd[1]: Starting D-Bus System Message Bus...
4月 08 18:26:14 masasin-arch systemd[1]: Started D-Bus System Message Bus.
It seems that there are no errors?
Offline
It seems that there are no errors?
At least not for the dbus service. Did you check the rest?
Googling your error, I find several threads where similar issues resulted from problems with the way filesystems are set up. Try and see if that helps (doesn't really get interesting until falconindy jumps in): https://bbs.archlinux.org/viewtopic.php?id=192053
Last edited by Raynman (2015-04-08 10:42:46)
Offline
-- Logs begin at 水 2013-08-21 08:01:49 JST, end at 水 2015-04-08 18:26:45 JST. --
4月 08 18:26:04 masasin-arch systemd-journal[132]: Journal started
4月 08 18:26:03 masasin-arch systemd-udevd[162]: starting version 218
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 2, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 4, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 6, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 8, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 10, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 12, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 14, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 16, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 18, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 20, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 22, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 24, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd[1]: Starting Flush Journal to Persistent Storage...
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 26, starting at character 1 ('S')
4月 08 18:26:04 masasin-arch systemd-udevd[162]: invalid key/value pair in file /etc/udev/rules.d/51-android.rules on line 28, starting at character 1 ('S')
etc until line 56.
There were also problems opening cups.socket and cups.path (no such file or directory), console-kit-daemon.service and display-manager.service (failed to load), but these were bold instead of red and bold.
Others from the kernel include:
ACPI Warning: SystemIO range 0x... conflicts with OPRegion 0x...
lpc_ich: Resource cfonflict(s) found affecting gpio_ich
r8169 0000:04:00.0: can'd disable ASPM; OS doesn't have ASPM control
CRAT table not found
I'll check out 51-android.rules in a couple of hours.
edit:
I removed it (backed up), and I still cannot systemd-logind.service. The offending lines all started with "SUBSYSTEM".
Last edited by masasin (2015-04-09 10:10:33)
Offline
same here. i handle this with poweroff instead reboot. but this worrkground not work all times (need 2 or 3 cycles).
but i can't enter to any shell (ssh inclusive) (chroot not tested)
Last edited by sl1pkn07 (2015-05-20 19:30:41)
Offline