systemd-analyze blame
8.228s apparmor.service
7.998s NetworkManager-wait-online.service
5.394s dev-sdb13.device
2.751s SuSEfirewall2_init.service
2.523s ModemManager.service
2.439s media-satadisk.mount
2.407s media-satadisk1.mount
2.360s display-manager.service
2.170s media-magacin.mount
1.879s systemd-rfkill.service
1.689s SuSEfirewall2.service
1.625s lm_sensors.service
1.518s teamviewerd.service
1.373s postfix.service
1.364s rc-local.service
1.357s nscd.service
1.314s systemd-journald.service
1.249s bluetooth.service
1.211s systemd-udevd.service
1.027s
systemd-fsck@dev-disk-by\x2duuid-fdf0d9b6\x2dc2db\x2d4c87\x2da3f4\x2d28b61319b70c.service
970ms media-rt2.mount
766ms systemd-journal-flush.service
693ms polkit.service
609ms ntpd.service
578ms NetworkManager.service
486ms systemd-remount-fs.service
478ms sys-kernel-debug.mount
476ms dev-mqueue.mount
474ms dev-hugepages.mount
390ms avahi-daemon.service
315ms systemd-tmpfiles-setup-dev.service
290ms auditd.service
215ms systemd-udev-root-symlink.service
213ms kmod-static-nodes.service
193ms systemd-modules-load.service
178ms systemd-sysctl.service
168ms dev-disk-by\x2duuid-c9cb5165\x2db6d3\x2d40cf\x2d90b4\x2dbff8cc9dc948.swap
153ms plymouth-read-write.service
131ms
[email protected]e