10-20-2018, 02:35 AM
I did try the recommendation you posted, but it did not help. Vbox service still active, even after unchecking in the Startup options.
On my PC I dual boot Linux Lite and another Linux distro.I deleted that distro off the partition and utilized the Boot Repair function of Linux Lite, then rebooted.Boot up time is a little bit faster, so I ran the Systemd-analyze Blame from the command line againHere is what came up:
systemd-analyze blame
17.881s vboxadd.service
12.986s plymouth-quit-wait.service
12.083s keyboard-setup.service
11.809s ufw.service
11.565s dev-sda5.device
11.019s systemd-journal-flush.service
5.484s motd-news.service
4.611s NetworkManager-wait-online.service
3.564s grub-common.service
3.417s accounts-daemon.service
3.208s ModemManager.service
3.170s NetworkManager.service
2.415s networkd-dispatcher.service
2.106s systemd-udevd.service
2.081s udisks2.service
1.760s thermald.service
1.759s apport.service
1.755s console-kit-log-system-start.service
1.721s systemd-logind.service
1.697s alsa-restore.service
1.692s lm-sensors.service
1.692s avahi-daemon.service
1.691s rsyslog.service
So, it appears that somehow dual booting was causing the problem ? I don't know.Also, don't know why vbox service still pops up, although with a much shorter time limit even after running those commands and unchecking vbox service in the Startup options.Does this mean it's resolved or is there something else going on ?
Thanks,
txm0523
On my PC I dual boot Linux Lite and another Linux distro.I deleted that distro off the partition and utilized the Boot Repair function of Linux Lite, then rebooted.Boot up time is a little bit faster, so I ran the Systemd-analyze Blame from the command line againHere is what came up:
systemd-analyze blame
17.881s vboxadd.service
12.986s plymouth-quit-wait.service
12.083s keyboard-setup.service
11.809s ufw.service
11.565s dev-sda5.device
11.019s systemd-journal-flush.service
5.484s motd-news.service
4.611s NetworkManager-wait-online.service
3.564s grub-common.service
3.417s accounts-daemon.service
3.208s ModemManager.service
3.170s NetworkManager.service
2.415s networkd-dispatcher.service
2.106s systemd-udevd.service
2.081s udisks2.service
1.760s thermald.service
1.759s apport.service
1.755s console-kit-log-system-start.service
1.721s systemd-logind.service
1.697s alsa-restore.service
1.692s lm-sensors.service
1.692s avahi-daemon.service
1.691s rsyslog.service
So, it appears that somehow dual booting was causing the problem ? I don't know.Also, don't know why vbox service still pops up, although with a much shorter time limit even after running those commands and unchecking vbox service in the Startup options.Does this mean it's resolved or is there something else going on ?
Thanks,
txm0523
Home Built PC: MOBO MSI 785GTM-E45, HDD West Dig 500 gb, Video Card AMD-ATI Radeon HD4200, Sound Card Radeon HD4200 Series RS880, Web Cam Creative Tech VF0415 Live Cam Vid IM ultra, Processor AMD Phenom 9750 Quad Core 2.4 gHz, RAM 8 GB Mushkin DDR2, Monitor Samsung S22B310, Samsung 2165w Laser printer, Linux Kernel version 4.4.0-linuxlite. Linuxlite 64 bit version 2.8