Slow boot on Xubuntu

Thank you so much for your responses.

When I type systemd-analyze blame, the following appears:

6.521s NetworkManager-wait-online.service
4.644s dev-sda6.device
3.148s dev-loop9.device
3.146s dev-loop8.device
2.880s snapd.service
2.832s dev-loop10.device
2.816s dev-loop12.device
2.806s dev-loop11.device
2.309s systemd-rfkill.service
1.654s keyboard-setup.service
942ms udisks2.service
797ms apparmor.service
765ms networkd-dispatcher.service
565ms NetworkManager.service
480ms snap-core18-1222.mount
471ms dev-loop0.device
470ms snap-wine\x2dplatform\x2d3\x2dstable-5.mount
464ms systemd-journald.service
455ms swapfile.swap
447ms dev-loop2.device
441ms snap-core18-1193.mount
440ms dev-loop3.device
433ms plymouth-quit-wait.service
410ms dev-loop6.device
404ms speech-dispatcher.service
403ms dev-loop1.device
401ms upower.service
383ms accounts-daemon.service
376ms ModemManager.service
374ms dev-loop5.device
371ms dev-loop4.device
371ms dev-loop7.device
353ms snap.bluez.bluez.service
344ms snap.bluez.obex.service
341ms systemd-udev-trigger.service
323ms systemd-timesyncd.service
311ms systemd-resolved.service
292ms grub-common.service
286ms systemd-logind.service
259ms lm-sensors.service
226ms snap-flacon\x2dtabetai-61.mount
213ms snap-gnome\x2d3\x2d28\x2d1804-92.mount
211ms pppd-dns.service
205ms snap-core-7916.mount
197ms systemd-journal-flush.service
190ms plymouth-start.service
189ms wpa_supplicant.service
180ms avahi-daemon.service
176ms rsyslog.service
167ms snap-gtk\x2dcommon\x2dthemes-1353.mount
164ms snap-core-7712.mount
163ms plymouth-read-write.service
153ms console-setup.service
151ms motd-news.service
148ms systemd-tmpfiles-setup.service
145ms snap-gtk\x2dcommon\x2dthemes-1313.mount
145ms snap-acrordrdc-6.mount
141ms user@1000.service
139ms lightdm.service
137ms snap-bluez-170.mount
132ms snap-wine\x2dplatform\x2druntime-55.mount
130ms snap-wine\x2dplatform\x2druntime-49.mount
116ms snapd.seeded.service
110ms systemd-modules-load.service
95ms thermald.service
92ms gpu-manager.service
79ms systemd-user-sessions.service
78ms colord.service
77ms polkit.service
77ms systemd-udevd.service
58ms packagekit.service
57ms systemd-tmpfiles-setup-dev.service
57ms systemd-sysctl.service
57ms sys-kernel-debug.mount
51ms dev-hugepages.mount
50ms systemd-random-seed.service
49ms ufw.service
48ms kmod-static-nodes.service
47ms systemd-update-utmp.service
42ms systemd-remount-fs.service
41ms hddtemp.service
40ms dev-mqueue.mount
34ms kerneloops.service
34ms sys-kernel-config.mount
31ms sys-fs-fuse-connections.mount
21ms apport.service
18ms systemd-tmpfiles-clean.service
15ms ureadahead-stop.service
12ms rtkit-daemon.service
11ms systemd-update-utmp-runlevel.service
10ms systemd-backlight@backlight:acpi_video0.service
6ms setvtrgb.service
5ms snapd.socket

AND IT IS NOT OVER!!!

-----------------------------------------------

When I type systemd-analyze critical-chain, it shows this:

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 @9.963s
└─multi-user.target @9.963s
└─hddtemp.service @9.921s +41ms
└─network-online.target @9.914s
└─NetworkManager-wait-online.service @3.392s +6.521s
└─NetworkManager.service @2.772s +565ms
└─dbus.service @2.737s
└─basic.target @2.733s
└─sockets.target @2.733s
└─snapd.socket @2.728s +5ms
└─sysinit.target @2.724s
└─apparmor.service @1.926s +797ms
└─local-fs.target @1.923s
└─run-snapd-ns-bluez.mnt.mount @5.437s
└─run-snapd-ns.mount @4.778s
└─local-fs-pre.target @1.918s
└─keyboard-setup.service @257ms +1.654s
└─systemd-journald.socket @254ms
└─system.slice @254ms
└─-.slice @248ms

AND IT IS NOT OVER because when I want to close the window, it says that a process is running but it doesn't progress.

------------------------------------------------------

When I type dmesg, there are plenty of lines in green and white as well as lines in red.

I imagine that the red ones might interest you, they say the following:

[18.844658] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:36:pipe A] flip_done timed out

[29.080619] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:36:pipe A] flip_done timed out
[39.320567] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:58:SVIDEO-1] flip_done timed out

[90.520624] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:36:pipe A] flip_done timed out
[100.760572] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:58:SVIDEO-1] flip_done timed out
[102.929821] IPv6: ADDRCONF(NETDEV_CHANGE): wlp11s0: link becomes ready
[113.560645] [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:43:pipe B] flip_done timed out
[113.664590] ------------[ cut here ]------------

[187.032722] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CRTC:43:pipe B] flip_done timed out
[197.272638] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR* [CONNECTOR:58:SVIDEO-1] flip_done timed out

Good evening again

Thank you.

Here is the information about the processors:
Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz

Intel(R) Core(TM)2 Duo CPU T5800 @ 2.00GHz

Here is the response for sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: LABEL="OS" UUID="787E34257E33DB18" TYPE="ntfs" PARTUUID="9593d3ca-01"
/dev/sda5: UUID="64B1CA6D0D7D9EEF" TYPE="ntfs" PTTYPE="dos" PARTUUID="9593d3ca-05"
/dev/sda6: UUID="5d639f41-1e57-454d-b625-540f9e4a566d" TYPE="ext4" PARTUUID="9593d3ca-06"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"

Here is the response for snap list
Name Version Revision Track Publisher Notes
acrordrdc 2018.011.20063 6 stable mmtrt -
bluez 5.47-3 170 stable canonical✓ -
core 16-2.42 7916 stable canonical✓ core
core18 20191010 1222 stable canonical✓ base
flacon-tabetai 5.4.0 61 stable lolsmth -
gnome-3-28-1804 3.28.0-14-g9303a49.9303a49 92 stable canonical✓ -
gtk-common-themes 0.1-25-gcc83164 1353 stable canonical✓ -
wine-platform-3-stable 3.0.4 5 stable mmtrt -
wine-platform-runtime v1.0 55 stable mmtrt

I found the famous etc/fstab, it tells me this:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system=""> <mount point=""> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=5d639f41-1e57-454d-b625-540f9e4a566d / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0

Good luck to you, all these commands are gibberish for now...
Djou</pass></dump></options></type></mount></file>

Yes, I have disabled the network by running the suggested command.

After the command systemd-analyze critical-chain, here’s what it says:
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 @9.959s
└─multi-user.target @9.959s
└─hddtemp.service @9.919s +39ms
└─network-online.target @9.916s
└─network.target @3.281s
└─NetworkManager.service @2.933s +347ms
└─dbus.service @2.871s
└─basic.target @2.639s
└─sockets.target @2.636s
└─snapd.socket @2.626s +6ms
└─sysinit.target @2.619s
└─apparmor.service @1.888s +729ms
└─local-fs.target @1.869s
└─run-snapd-ns-bluez.mnt.mount @5.535s
└─run-snapd-ns.mount @4.941s
└─local-fs-pre.target @1.854s
└─keyboard-setup.service @309ms +1.543s
└─systemd-journald.socket @257ms
└─system.slice @256ms
└─-.slice @251ms

I don't know what the 10GB partition is for; maybe it’s for Windows 7 which is installed in dual boot.
How can I find out?

Thank you so much!!!!!!!

Thank you thank you
For your information, when I start, the Xubuntu welcome screen never appears while it does appear when shutting down.

When I turn on the PC, now there are 5 or 6 lines of white color with data and ERROR written on them.

This might help perhaps.

Also, the PC cools down when I launch the internet. Not when I am using offline software.

Then, I downloaded a diagnostic software and it starts with this screen



thank you to you

Thank you all! And especially you, jns55!!!
A fellow user gave me the solution that I'm sharing with you; now my PC starts in less than 5 seconds:

With the gedit editor

sudo gedit /etc/default/grub

---------------------------------------------

Add this line:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video=SVIDEO-1:d"

You can also change these lines at the same time:

---------------------------------------------------

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5

--------------------------------------------------

You save

sudo update-grub

sudo reboot

Have a nice day, everyone!
djou