Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Mär 02 18:29:08 arch login[259]: pam_unix(login:session): session opened for user root by (uid=0)
- Mär 02 18:29:08 arch dbus[257]: [system] Activating systemd to hand-off: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service'
- Mär 02 18:29:24 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
- Mär 02 18:29:24 arch dbus[257]: [system] Successfully activated service 'org.freedesktop.login1'
- Mär 02 18:29:24 arch systemd-logind[256]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
- Mär 02 18:29:24 arch systemd-logind[256]: Watching system buttons on /dev/input/event3 (Power Button)
- Mär 02 18:29:24 arch systemd-logind[256]: Watching system buttons on /dev/input/event2 (Power Button)
- Mär 02 18:29:24 arch systemd-logind[256]: New seat seat0.
- Mär 02 18:29:33 arch login[259]: pam_systemd(login:session): Failed to create 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.
- Mär 02 18:29:33 arch login[259]: ROOT LOGIN ON tty1
- Mär 02 18:29:49 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
- Mär 02 18:29:49 arch systemd-logind[256]: Failed to start unit user-0.slice: 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.
- Mär 02 18:29:49 arch systemd-logind[256]: Failed to start user slice: 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.
- Mär 02 18:30:14 arch systemd-logind[256]: Failed to start unit user@0.service: 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.
- Mär 02 18:30:14 arch systemd-logind[256]: Failed to start user service: 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.
- Mär 02 18:30:14 arch systemd-logind[256]: Assertion 's->user->slice' failed at src/login/logind-session.c:502, function session_start_scope(). Aborting.
- Mär 02 18:30:14 arch dbus[257]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
- Mär 02 18:30:15 arch systemd-coredump[360]: Process 256 (systemd-logind) dumped core.
- Mär 02 18:30:15 arch systemd[1]: systemd-logind.service: main process exited, code=dumped, status=6/ABRT
- Mär 02 18:30:15 arch systemd[1]: Failed to start Login Service.
- Mär 02 18:30:15 arch systemd[1]: Unit systemd-logind.service entered failed state.
- Mär 02 18:30:15 arch systemd[1]: Starting Multi-User System.
- Mär 02 18:30:15 arch systemd[1]: Reached target Multi-User System.
- Mär 02 18:30:15 arch systemd[1]: Starting Graphical Interface.
- Mär 02 18:30:15 arch systemd[1]: Reached target Graphical Interface.
- Mär 02 18:30:15 arch systemd[1]: Startup finished in 1.419s (kernel) + 1min 15.790s (userspace) = 1min 17.210s.
- Mär 02 18:30:15 arch systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
- Mär 02 18:30:15 arch systemd[1]: Stopping Login Service...
- Mär 02 18:30:15 arch systemd[1]: Starting Login Service...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement