我的 Ubuntu 17.10 启动时间太长，很多人都遇到了同样的问题，但我没有看到正确的答案。
为什么 nmbd.service 需要 1 分钟才能启动？
这是结果sudo systemd-analyze blame
1min 1.679s nmbd.service
16.662s plymouth-quit-wait.service
15.172s dev-sda2.device
13.391s apparmor.service
9.423s snapd.service
8.600s NetworkManager-wait-online.service
7.266s [email protected]
7.209s udisks2.service
6.632s mysql.service
6.579s accounts-daemon.service
6.566s NetworkManager.service
6.232s ModemManager.service
4.965s apport.service
4.785s teamviewerd.service
4.484s networking.service
4.325s speech-dispatcher.service
3.912s rsyslog.service
3.742s iio-sensor-proxy.service
3.663s gpu-manager.service
3.306s systemd-rfkill.service
3.031s avahi-daemon.service
3.023s fwupd.service
2.762s polkit.service
2.524s virtualbox.service
2.384s grub-common.service
1.723s dev-loop2.device
1.683s dev-loop0.device
1.669s binfmt-support.service
1.649s console-setup.service
1.573s systemd-timesyncd.service
1.512s winbind.service
1.459s dev-loop1.device
1.394s systemd-tmpfiles-setup.service
1.253s smbd.service
1.234s thermald.service
1.108s systemd-udevd.service
1.103s packagekit.service
1.093s dns-clean.service
1.065s resolvconf.service
1.048s upower.service
1.047s systemd-random-seed.service
1.025s systemd-modules-load.service
919ms keyboard-setup.service
884ms [email protected]
678ms systemd-logind.service
663ms systemd-udev-trigger.service
642ms systemd-tmpfiles-setup-dev.service
587ms gdm.service
532ms pppd-dns.service
521ms systemd-journal-flush.service
478ms systemd-update-utmp.service
466ms systemd-journald.service
411ms systemd-resolved.service
364ms snap-core-3247.mount
319ms wpa_supplicant.service
288ms hddtemp.service
275ms kerneloops.service
274ms systemd-backlight@backlight:acpi_video0.service
263ms kmod-static-nodes.service
240ms snap-core-3440.mount
230ms dev-hugepages.mount
192ms [email protected]
我怎样才能解决这个问题 ？