![]() Ignoring: Failed to activate service '1': timed ![]() Systemd-logind: Failed to start user slice user-0.slice, Systemd-logind: Failed to stop user slice: Failed to activate Systemd-logind: Failed to stop user service: Failed to activate Systemd-logind: Failed to start session scope session-11.scope:įailed to activate service '1': timed out Systemd-logind: Failed to start user service, ignoring: Failed toĪctivate service '1': timed out User-0.slice, ignoring: Connection timed out Sep 26 11:51:21 govern systemd-logind: Failed to start user slice Tasks: 1 (limit: 4915) CGroup: /system.slice/rvice Main PID: 667 (systemd-logind) Status: "Processing requests." * rvice - Login Service Loaded: loaded (/lib/systemd/system/rvice static vendor preset:Įnabled) Active: active (running) since Wed 11:37:57 ![]() To try to get some understanding of this, I ran the systemctl status command suggested in some reports: The system is extremely slow performance, particularly at logon - even the console logon is very slow.ĭbus-daemon: Activated service This looks similar to dbus errors I see reported, but they are supposed to be fixed.
0 Comments
Leave a Reply. |