system-d analyze blame 16.989s apt-daily.service 12.232s NetworkManager-wait-online.service 6.472s dev-sda7.device 2.832s nmbd.service 2.830s winbind.service 2.700s samba-ad-dc.service 2.093s NetworkManager.service 2.078s apparmor.service 1.572s ModemManager.service 1.539s minidlna.service 1.488s thermald.service 1.362s systemd-udevd.service 1.246s accounts-daemon.service 1.194s keyboard-setup.service 1.011s systemd-fsck@dev-disk-by\x2duuid-e7396805\x2dec9a\x2d420c\x2d9bf4\x2d185fe0ed241d.service 949ms lightdm.service 908ms grub-common.service 874ms console-setup.service 767ms udisks2.service 674ms apport.service 657ms gpu-manager.service 644ms systemd-tmpfiles-setup-dev.service 631ms systemd-modules-load.service 567ms sys-kernel-debug.mount 503ms polkitd.service 479ms systemd-tmpfiles-setup.service 473ms colord.service 425ms avahi-daemon.service 422ms systemd-logind.service 399ms dev-mqueue.mount 395ms dev-hugepages.mount 394ms binfmt-support.service 384ms upower.service 384ms ondemand.service 375ms speech-dispatcher.service 375ms ufw.service 359ms console-kit-log-system-start.service 359ms networking.service 356ms lm-sensors.service 352ms systemd-user-sessions.service 349ms rsyslog.service 317ms plymouth-start.service 311ms systemd-journald.service 305ms home.mount 294ms smbd.service 280ms systemd-fsck@dev-disk-by\x2duuid-debd7b07\x2d13f9\x2d49f5\x2daf44\x2d1f458a37514d.service 244ms dns-clean.service 228ms irqbalance.service 215ms systemd-udev-trigger.service 181ms systemd-update-utmp.service 175ms kmod-static-nodes.service 151ms systemd-sysctl.service 137ms systemd-random-seed.service 113ms wpa_supplicant.service 100ms systemd-timesyncd.service 95ms systemd-journal-flush.service 80ms user@1000.service 78ms snapd.autoimport.service 74ms plymouth-read-write.service 72ms home-Comun.mount 60ms systemd-remount-fs.service 44ms setvtrgb.service 44ms resolvconf.service 29ms alsa-restore.service 22ms proc-sys-fs-binfmt_misc.mount 15ms pppd-dns.service 14ms ureadahead-stop.service 8ms rc-local.service 5ms plymouth-quit-wait.service 4ms systemd-update-utmp-runlevel.service 4ms rtkit-daemon.service 2ms sys-fs-fuse-connections.mount 2ms snapd.socket systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @1min 50.778s └─multi-user.target @1min 50.778s └─smbd.service @1min 50.483s +294ms └─nmbd.service @1min 47.635s +2.832s └─network-online.target @1min 47.616s └─NetworkManager-wait-online.service @1min 35.383s +12.232s └─NetworkManager.service @1min 33.279s +2.093s └─dbus.service @1min 32.966s └─basic.target @1min 32.942s └─sockets.target @1min 32.942s └─snapd.socket @1min 32.940s +2ms └─sysinit.target @1min 32.906s └─apparmor.service @10.296s +2.078s └─local-fs.target @10.237s └─run-user-1000-gvfs.mount @2min 50.754s └─run-user-1000.mount @2min 48.138s └─local-fs-pre.target @5.336s └─systemd-remount-fs.service @5.275s +60ms └─system.slice @2.863s └─-.slice @2.736s