25th September 2017, 21:03
Thanks for the response. Here are the results of systemd-analyze critcal-chain. A couple things pop up there, but not sure what they all mean.
I never came across the virtualbox-guest issue. I'll look into that. I do use virtualbox and the guest additions.
I've also noticed Plymouth doesn't work and I am unable to change the plymouth splash screen. So it could have been something with the recent plymouth update as well.
Thank you for your time.
I never came across the virtualbox-guest issue. I'll look into that. I do use virtualbox and the guest additions.
I've also noticed Plymouth doesn't work and I am unable to change the plymouth splash screen. So it could have been something with the recent plymouth update as well.
Thank you for your time.
Code:
systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @22.850s
└─multi-user.target @22.850s
└─smbd.service @22.601s +248ms
└─nmbd.service @22.198s +387ms
└─network-online.target @6.807s
└─NetworkManager-wait-online.service @1.047s +5.759s
└─NetworkManager.service @883ms +150ms
└─dbus.service @856ms
└─basic.target @851ms
└─sockets.target @850ms
└─snapd.socket @835ms +14ms
└─sysinit.target @833ms
└─apparmor.service @766ms +67ms
└─local-fs.target @765ms
└─run-user-1000.mount @2.117s
└─local-fs-pre.target @235ms
└─systemd-remount-fs.service @225ms +8ms
└─systemd-journald.socket @104ms
└─-.slice @92ms