systemd-analyze time
Startup finished in 11.691s (kernel) + 32.096s (userspace) = 43.787s
graphical.target reached after 32.083s in userspace
systemd-analyze blame
12.169s udisks2.service
11.063s accounts-daemon.service
10.845s networkd-dispatcher.service
9.625s dev-sda2.device
9.091s NetworkManager-wait-online.service
8.423s polkit.service
8.136s snapd.service
6.906s bluetooth.service
6.900s avahi-daemon.service
6.899s NetworkManager.service
6.888s iio-sensor-proxy.service
6.594s thermald.service
6.590s wpa_supplicant.service
6.587s systemd-logind.service
5.499s systemd-journal-flush.service
4.053s gpu-manager.service
2.982s rsyslog.service
2.875s packagekit.service
2.597s grub-initrd-fallback.service
2.435s apparmor.service
2.329s grub-common.service
2.103s ModemManager.service
2.077s bolt.service
2.053s systemd-udevd.service
1.629s e2scrub_reap.service
1.588s apport.service
1.328s systemd-resolved.service
1.101s systemd-modules-load.service
907ms systemd-backlight@backlight:acpi_video0.service
904ms systemd-backlight@backlight:radeon_bl0.service
882ms systemd-tmpfiles-setup.service
811ms systemd-random-seed.service
804ms systemd-sysusers.service
542ms systemd-sysctl.service
489ms upower.service
462ms systemd-tmpfiles-setup-dev.service
365ms systemd-remount-fs.service
355ms systemd-update-utmp.service
338ms keyboard-setup.service
327ms alsa-restore.service
315ms systemd-rfkill.service
309ms systemd-timesyncd.service
280ms pppd-dns.service
280ms setvtrgb.service
270ms systemd-user-sessions.service
245ms sddm.service
228ms systemd-fsck@dev-disk-by\x2duuid-8EA8\x2dFD8F.service
223ms systemd-journald.service
215ms snapd.seeded.service
210ms console-setup.service
208ms snapd.apparmor.service
208ms kmod-static-nodes.service
203ms swapfile.swap
197ms kerneloops.service
191ms systemd-udev-trigger.service
184ms ufw.service
108ms user@1000.service
89ms boot-efi.mount
66ms plymouth-read-write.service
65ms dev-hugepages.mount
65ms dev-mqueue.mount
64ms sys-kernel-debug.mount
64ms sys-kernel-tracing.mount
27ms rtkit-daemon.service
23ms plymouth-quit.service
15ms user-runtime-dir@1000.service
13ms plymouth-start.service
10ms systemd-update-utmp-runlevel.service
2ms sys-fs-fuse-connections.mount
2ms sys-kernel-config.mount
626us snapd.socket
388us clean-mount-point@media-chakri-MYLINUXLIVE.service
La ca s'arrete pas ,il faut fermer la Konsole
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @32.083s
└─multi-user.target @32.083s
└─kerneloops.service @31.885s +197ms
└─network-online.target @31.766s
└─NetworkManager-wait-online.service @22.674s +9.091s
└─NetworkManager.service @15.772s +6.899s
└─dbus.service @15.769s
└─basic.target @15.747s
└─sockets.target @15.747s
└─snapd.socket @15.746s +626us
└─sysinit.target @15.710s
└─snapd.apparmor.service @15.501s +208ms
└─apparmor.service @13.027s +2.435s
└─local-fs.target @13.026s
└─boot-efi.mount @12.937s +89ms
└─systemd-fsck@dev-disk-by\x2duuid-8EA8\x2dFD8F.service @12.663s +228ms
└─dev-disk-by\x2duuid-8EA8\x2dFD8F.device @12.662s
