(4th October 2016, 18:28)leszek Wrote: What how is that even possible that it got longer xD
What does systemd-analyze blame show you exactly?
6.939s NetworkManager-wait-online.service
1.253s gpu-manager.service
951ms dev-mapper-maui\x2d\x2dvg\x2droot.device
693ms smbd.service
489ms nmbd.service
416ms samba-ad-dc.service
384ms accounts-daemon.service
375ms ModemManager.service
289ms upower.service
261ms iio-sensor-proxy.service
202ms grub-common.service
202ms systemd-udev-trigger.service
200ms irqbalance.service
190ms virtualbox-guest-utils.service
169ms apparmor.service
152ms NetworkManager.service
147ms bluetooth.service
[font=monospace] 142ms systemd-logind.service
138ms rsyslog.service
134ms avahi-daemon.service
134ms virtualbox.service
129ms console-setup.service
125ms preload.service
110ms ondemand.service
104ms networking.service
85ms systemd-journald.service
80ms snapd.firstboot.service
75ms udisks2.service
70ms polkitd.service
61ms keyboard-setup.service
51ms pppd-dns.service
50ms systemd-journal-flush.service
46ms lvm2.service
44ms alsa-restore.service
41ms thermald.service
33ms systemd-modules-load.service
33ms lm-sensors.service
32ms systemd-tmpfiles-setup.service
32ms user@1000.service
30ms hddtemp.service
30ms systemd-fsck@dev-disk-by\x2duuid-904D\x2d6D63.service
30ms boot-efi.mount
28ms systemd-user-sessions.service
26ms systemd-tmpfiles-clean.service
24ms plymouth-quit.service
23ms systemd-udevd.service
22ms plymouth-start.service
22ms systemd-update-utmp.service
21ms resolvconf.service
21ms kmod-static-nodes.service
21ms systemd-fsck@dev-disk-by\x2duuid-f0cdaeac\x2deac3\x2d4318\x2d9757\x2ddd23c96d903d.serv
19ms boot.mount
16ms dev-mqueue.mount
14ms dev-hugepages.mount
14ms systemd-update-utmp-runlevel.service
14ms wpa_supplicant.service
12ms plymouth-read-write.service
[/font]