Very slow boot time Kubunto Plasma 5

[Timnewton30]

Newbie asking for help please.
Boot time is extremely slow, can anyone understand/explain the following for me please after running a check ?

tim@tim-wyse5070extendedthinclient:~$ 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 @25.150s
└─multi-user.target @25.150s
└─smbd.service @24.956s +193ms
└─nmbd.service @24.665s +279ms
└─network-online.target @24.632s
└─NetworkManager-wait-online.service @7.571s +17.058s
└─NetworkManager.service @5.841s +1.721s
└─dbus.service @5.341s +280ms
└─basic.target @5.320s
└─sockets.target @5.320s
└─libvirtd-ro.socket @5.320s
└─libvirtd.socket @5.309s +9ms
└─sysinit.target @5.300s
└─systemd-udev-settle.service @1.468s +3.822s
└─systemd-udev-trigger.service @937ms +517ms
└─systemd-udevd-kernel.socket @865ms
└─system.slice @838ms
└─-.slice @838ms
tim@tim-wyse5070extendedthinclient:~$

[claydoh]

Boot time is extremely slow,

What is extremely slow? How long in total?
Can you give some base system specs?
Was it always slow, or is it new?

It helps to look at the whole picture

systemd-analyze
systemd-analyze blame
​systemd-analyze critical-chain

NetworkManager-wait-online.service @7.571s +17.058s

This is a bit obvious at first glance, but this also seems to indicate other things are taking as long time as well:

graphical.target @25.150s

'


NetworkManager-wait-online.service is somewhat common, and can be found searching here or on the general web, and it is fairly easy to test.

[Timnewton30]

Thanks claydoh.
About 2 to 3 minutes to reach log-in screen. This is a recent development.

Running a Dell Wyse 5070 Thin client, 4x core Intel Pentium Silver J5005 CPU @1.5Ghz (1.8Ghz boost), 16Gb Ram (15.4Gb free, my normal running), 254gb SSD (218.7Gb free).

The PC used to log-in quickly, then i would get a very quick half second 'pop-up' after logging in as it found the network (Ethernet, not Wi-Fi). This pop up has now disappeared, so I'm assuming connection is being searched for before a log-in attempt ? That said, surely Ethernet connection shouldn't take so long.

I am further wondering if these are relevant ? └─smbd.service @24.956s +193ms
└─nmbd.service @24.665s +279ms

Hope I've explained a little more. I'm new to this sorry.

Best
Tim

[Timnewton30]

What is extremely slow? How long in total?
Can you give some base system specs?
Was it always slow, or is it new?

It helps to look at the whole picture

systemd-analyze
systemd-analyze blame
​systemd-analyze critical-chain

This is a bit obvious at first glance, but this also seems to indicate other things are taking as long time as well:
'


NetworkManager-wait-online.service is somewhat common, and can be found searching here or on the general web, and it is fairly easy to test.

tim@tim-wyse5070extendedthinclient:~$ systemd-analyze
Startup finished in 33.238s (firmware) + 7.782s (loader) + 1min 33.289s (kernel) + 25.244s (userspace) = 2min 39.555s
graphical.target reached after 25.150s in userspace.
tim@tim-wyse5070extendedthinclient:~$ systemd-analyze blame
17.058s NetworkManager-wait-online.service
4.272s apt-daily-upgrade.service
3.822s systemd-udev-settle.service
3.291s fwupd.service
1.855s snapd.seeded.service
1.721s NetworkManager.service
1.131s dev-sda2.device
1.057s snapd.service
803ms apport.service
681ms accounts-daemon.service
608ms polkit.service
608ms power-profiles-daemon.service
547ms udisks2.service
517ms systemd-udev-trigger.service
509ms rsyslog.service
507ms apparmor.service
501ms user@1000.service
490ms avahi-daemon.service
467ms secureboot-db.service
440ms systemd-resolved.service
433ms grub-common.service
419ms gpu-manager.service
lines 1-22...skipping...
17.058s NetworkManager-wait-online.service
4.272s apt-daily-upgrade.service
3.822s systemd-udev-settle.service
3.291s fwupd.service
1.855s snapd.seeded.service
1.721s NetworkManager.service
1.131s dev-sda2.device
1.057s snapd.service
803ms apport.service
681ms accounts-daemon.service
608ms polkit.service
608ms power-profiles-daemon.service
547ms udisks2.service
517ms systemd-udev-trigger.service
509ms rsyslog.service
507ms apparmor.service
501ms user@1000.service
490ms avahi-daemon.service
467ms secureboot-db.service
440ms systemd-resolved.service
433ms grub-common.service
419ms gpu-manager.service
398ms lm-sensors.service
370ms dev-loop10.device
366ms systemd-journald.service
365ms dev-loop5.device
364ms dev-loop16.device
361ms dev-loop13.device
357ms dev-loop9.device
356ms dev-loop1.device
355ms dev-loop6.device
354ms qemu-kvm.service
351ms dev-loop2.device
347ms switcheroo-control.service
345ms dev-loop3.device
344ms dev-loop14.device
334ms dev-loop7.device
327ms snapd.apparmor.service
324ms systemd-modules-load.service
324ms dev-loop8.device
322ms dev-loop4.device
320ms systemd-timesyncd.service
317ms dev-loop12.device
316ms dev-loop15.device
314ms systemd-binfmt.service
311ms dev-loop0.device
304ms dev-loop11.device
299ms e2scrub_reap.service
283ms systemd-machined.service
280ms dbus.service
279ms nmbd.service
272ms apport-autoreport.service
272ms update-notifier-download.service
269ms thermald.service
249ms upower.service
222ms systemd-udevd.service
lines 1-56

[claydoh]

I am further wondering if these are relevant ? └─smbd.service @24.956s +193ms
└─nmbd.service @24.665s +279ms

No, these are adding milliseconds. A half second.

So what about the full set of commands I listed above? Seeing the whole picture can help a lot.

[Timnewton30]

im@tim-wyse5070extendedthinclient:~$ systemd-analyze
Startup finished in 33.238s (firmware) + 7.782s (loader) + 1min 33.289s (kernel) + 25.244s (userspace) = 2min 39.
555s
graphical.target reached after 25.150s in userspace.
tim@tim-wyse5070extendedthinclient:~$ systemd-analyze blame
17.058s NetworkManager-wait-online.service
4.272s apt-daily-upgrade.service
3.822s systemd-udev-settle.service
3.291s fwupd.service
1.855s snapd.seeded.service
1.721s NetworkManager.service
1.131s dev-sda2.device
1.057s snapd.service
803ms apport.service
681ms accounts-daemon.service
608ms polkit.service
608ms power-profiles-daemon.service
547ms udisks2.service
517ms systemd-udev-trigger.service
509ms rsyslog.service
507ms apparmor.service
501ms user@1000.service
490ms avahi-daemon.service
467ms secureboot-db.service
440ms systemd-resolved.service
433ms grub-common.service
419ms gpu-manager.service


tim@tim-wyse5070extendedthinclient:~$ 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 @25.150s
└─multi-user.target @25.150s
└─smbd.service @24.956s +193ms
└─nmbd.service @24.665s +279ms
└─network-online.target @24.632s
└─NetworkManager-wait-online.service @7.571s +17.058s
└─NetworkManager.service @5.841s +1.721s
└─dbus.service @5.341s +280ms
└─basic.target @5.320s
└─sockets.target @5.320s
└─libvirtd-ro.socket @5.320s
└─libvirtd.socket @5.309s +9ms
└─sysinit.target @5.300s
└─systemd-udev-settle.service @1.468s +3.822s
└─systemd-udev-trigger.service @937ms +517ms
└─systemd-udevd-kernel.socket @865ms
└─system.slice @838ms
└─-.slice @838ms

[Timnewton30]

Network Manager-wait-online.service is showing the following dependencies.......

systemctl list-dependencies --reverse network-online.target
network-online.target
● ├─cups-browsed.service
○ ├─fwupd-refresh.service
● ├─nmbd.service
○ ├─samba-ad-dc.service
● ├─smbd.service
○ └─whoopsie.service


Would a disable or mask command help ?