Opa, aproveitando aqui.
Eu to com mesmo problema, segue as saidas.
Startup finished in 4.621s (kernel) + 1min 43.529s (userspace) = 1min 48.150s
graphical.target reached after 1min 43.508s in userspace
6.985s NetworkManager-wait-online.service
4.509s plymouth-quit-wait.service
2.007s dev-sda1.device
1.899s snapd.service
1.291s smartmontools.service
1.154s systemd-logind.service
1.134s snap-spotify-41.mount
1.113s snap-gtk\x2dcommon\x2dthemes-1506.mount
1.104s snap-snapd-8140.mount
1.076s snap-vlc-1620.mount
1.070s rc-local.service
1.060s snap-whatsdesk-19.mount
1.049s snap-snapd-7777.mount
1.039s upower.service
993ms man-db.service
984ms dev-loop3.device
975ms snap-vlc-1700.mount
928ms snap-snap\x2dstore-454.mount
831ms dev-loop2.device
815ms dev-loop7.device
731ms udisks2.service
729ms dev-loop8.device
722ms systemd-journald.service
695ms dev-loop9.device
690ms dev-loop10.device
688ms dev-loop5.device
641ms systemd-resolved.service
636ms networkd-dispatcher.service
632ms dev-loop11.device
604ms systemd-timesyncd.service
579ms accounts-daemon.service
553ms snap-gtk2\x2dcommon\x2dthemes-9.mount
545ms dev-loop4.device
530ms snap-core18-1705.mount
523ms dev-loop6.device
521ms dev-loop0.device
508ms snap-chromium-1192.mount
441ms dev-loop12.device
434ms snap-gimp-273.mount
429ms snap-gnome\x2d3\x2d34\x2d1804-36.mount
418ms dev-loop1.device
409ms snap-canonical\x2dlivepatch-95.mount
399ms avahi-daemon.service
391ms fwupd.service
390ms polkit.service
388ms NetworkManager.service
380ms logrotate.service
334ms grub-common.service
329ms systemd-rfkill.service
312ms snap-chromium-1193.mount
306ms apport.service
301ms snap-gnome\x2d3\x2d28\x2d1804-128.mount
267ms dev-loop13.device
259ms apport-autoreport.service
247ms snap-snap\x2dstore-433.mount
244ms grub-initrd-fallback.service
239ms lm-sensors.service
235ms nmbd.service
234ms dev-loop14.device
230ms rsyslog.service
222ms snap-gnome\x2d3\x2d34\x2d1804-24.mount
207ms switcheroo-control.service
203ms e2scrub_reap.service
203ms gpu-manager.service
202ms thermald.service
199ms wpa_supplicant.service
193ms ModemManager.service
188ms pppd-dns.service
174ms user@1000.service
164ms systemd-modules-load.service
163ms systemd-udev-trigger.service
161ms teamviewerd.service
152ms systemd-journal-flush.service
131ms smbd.service
117ms snap-core18-1754.mount
116ms colord.service
116ms snap-core-9289.mount
108ms systemd-udevd.service
105ms keyboard-setup.service
94ms apparmor.service
94ms dev-loop15.device
88ms dev-loop18.device
87ms snapd.apparmor.service
86ms dev-loop17.device
81ms systemd-tmpfiles-setup.service
68ms dev-loop19.device
62ms dev-loop16.device
54ms packagekit.service
43ms gdm.service
36ms snapd.seeded.service
33ms rtkit-daemon.service
32ms plymouth-start.service
24ms kerneloops.service
24ms alsa-restore.service
23ms systemd-sysctl.service
21ms console-setup.service
20ms user-runtime-dir@1000.service
19ms dev-hugepages.mount
19ms modprobe@drm.service
18ms dev-mqueue.mount
18ms systemd-sysusers.service
17ms plymouth-read-write.service
17ms sys-kernel-debug.mount
16ms sys-kernel-tracing.mount
16ms systemd-random-seed.service
15ms systemd-remount-fs.service
14ms systemd-tmpfiles-setup-dev.service
13ms systemd-update-utmp-runlevel.service
12ms kmod-static-nodes.service
12ms systemd-update-utmp.service
11ms sys-fs-fuse-connections.mount
11ms systemd-user-sessions.service
10ms openvpn.service
9ms sys-kernel-config.mount
6ms ufw.service
5ms setvtrgb.service
836us snapd.socket
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 @1min 43.508s
└─multi-user.target @1min 43.507s
└─rc-local.service @1min 37.920s +1.070s
└─network-online.target @1min 37.916s
└─NetworkManager-wait-online.service @1min 30.929s +6.985s
└─NetworkManager.service @1min 30.539s +388ms
└─dbus.service @1min 30.533s
└─basic.target @1min 30.516s
└─sockets.target @1min 30.516s
└─snapd.socket @1min 30.515s +836us
└─sysinit.target @1min 30.506s
└─systemd-timesyncd.service @1.753s +604ms
└─systemd-tmpfiles-setup.service @1.658s +81ms
└─local-fs.target @1.643s
└─run-snapd-ns-canonical\x2dlivepatch.mnt.mount @1min 31.541s
└─run-snapd-ns.mount @1min 31.215s
└─local-fs-pre.target @451ms
└─keyboard-setup.service @345ms +105ms
└─systemd-journald.socket @337ms
└─-.mount @334ms
└─system.slice @334ms
└─-.slice @334ms
# /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/sda1 during installation
UUID=190d5511-e3ae-4d60-bea6-14097791847b / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=7b18f2a5-ffc5-49f5-b8bc-71fbe5bf8471 none swap sw 0 0
# swap was on /dev/sdd1 during installation
UUID=482956a0-c6f2-4bd6-9c55-5a5d8f94db52 none swap sw 0 0
Olá xgleymer, favor abrir o terminal e executar os seguintes comandos, copie o cole aqui as saídas deles para gente analizar:
sudo systemd-analyze
sudo systemd-analyze blame
systemd-analyze critical-chain
sudo cat /etc/fstab
No aguardo.