我以新用户身份使用 Ubuntu 19.04。从一开始安装它，它似乎需要花费太多时间来启动。最近我升级到 Ubuntu2 0.04，但问题尚未解决。我在这里查找了几个类似的问题，但我自己无法找到解决方案。请注意，我使用 windows10 双启动，Windows 似乎启动时间要少得多。我确实认为原因在某种程度上是图形...
我的电脑规格：带集成显卡的 AMD Ryzen 2200G。16 GB Ram @ 2666Mz Asus Prime A320M-K 主板。Linux 安装在 500GB 的 HDD 上
以下是 systemd-analyze blame 的输出
tejas@tejas-System-Product-Name:~$ sudo systemd-analyze blame
[sudo] password for tejas:
40.445s plymouth-quit-wait.service
25.389s snapd.service
24.305s networkd-dispatcher.service
23.674s udisks2.service
15.360s dev-sdb2.device
14.352s accounts-daemon.service
14.304s ModemManager.service
10.949s NetworkManager-wait-online.service
10.479s polkit.service
9.799s avahi-daemon.service
9.793s NetworkManager.service
9.665s switcheroo-control.service
9.657s wpa_supplicant.service
9.656s thermald.service
9.653s systemd-logind.service
8.424s dev-loop10.device
7.294s dev-loop11.device
7.105s dev-loop8.device
7.080s dev-loop9.device
6.908s dev-loop12.device
6.373s dev-loop13.device
6.287s dev-loop0.device
6.203s dev-loop1.device
5.819s systemd-resolved.service
5.793s systemd-journal-flush.service
5.537s dev-loop4.device
5.362s dev-loop3.device
5.101s dev-loop5.device
5.039s dev-loop2.device
5.022s rsyslog.service
4.955s dev-loop6.device
4.876s dev-loop7.device
3.754s grub-initrd-fallback.service
3.305s systemd-udevd.service
3.265s gdm.service
3.227s grub-common.service
2.779s colord.service
2.579s fwupd.service
2.516s apport.service
2.289s e2scrub_reap.service
2.220s gpu-manager.service
2.069s [email protected]
1.845s systemd-fsck@dev-disk-by\x2duuid-75DC\x2d8465.service
1.689s apparmor.service
1.327s systemd-modules-load.service
1.257s systemd-tmpfiles-setup.service
1.254s systemd-sysusers.service
1.250s systemd-tmpfiles-setup-dev.service
1.061s snap-gnome\x2d3\x2d34\x2d1804-33.mount
1.050s systemd-random-seed.service
1.048s snap-inkscape-7627.mount
990ms snapd.apparmor.service
963ms systemd-sysctl.service
850ms [email protected]
791ms swapfile.swap
752ms systemd-timesyncd.service
739ms kerneloops.service
700ms keyboard-setup.service
588ms upower.service
563ms snap-core-9066.mount
557ms snap-gtk\x2dcommon\x2dthemes-1506.mount
541ms snap-atom-250.mount
530ms dev-hugepages.mount
530ms dev-mqueue.mount
529ms sys-kernel-debug.mount
528ms sys-kernel-tracing.mount
526ms systemd-journald.service
525ms kmod-static-nodes.service
524ms snap-core-8935.mount
477ms snapd.seeded.service
470ms snap-gtk\x2dcommon\x2dthemes-1502.mount
426ms snap-core18-1754.mount
423ms snap-julia-13.mount
418ms snap-gnome\x2d3\x2d34\x2d1804-27.mount
398ms systemd-user-sessions.service
387ms systemd-udev-trigger.service
367ms snap-gtk2\x2dcommon\x2dthemes-9.mount
345ms ufw.service
315ms pppd-dns.service
301ms openvpn.service
270ms rtkit-daemon.service
256ms snap-eclipse-48.mount
222ms snap-core18-1705.mount
210ms plymouth-start.service
186ms systemd-remount-fs.service
179ms console-setup.service
178ms snap-gnome\x2d3\x2d28\x2d1804-116.mount
169ms boot-efi.mount
162ms systemd-tmpfiles-clean.service
116ms systemd-update-utmp.service
113ms setvtrgb.service
104ms [email protected]
61ms plymouth-read-write.service
12ms systemd-update-utmp-runlevel.service
11ms alsa-restore.service
4ms sys-fs-fuse-connections.mount
3ms sys-kernel-config.mount
1ms snapd.socket
371us [email protected]
以下是 systemd-analyze critical chain 的输出
tejas@tejas-System-Product-Name:~$ 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 @1min 27.584s
└─multi-user.target @1min 27.583s
└─kerneloops.service @59.503s +175ms
└─network-online.target @59.441s
└─NetworkManager-wait-online.service @44.400s +15.039s
└─NetworkManager.service @27.374s +17.024s
└─dbus.service @27.371s
└─basic.target @27.133s
└─sockets.target @27.133s
└─snapd.socket @27.132s +896us
└─sysinit.target @26.807s
└─snapd.apparmor.service @25.934s +872ms
└─apparmor.service @24.152s +1.781s
└─local-fs.target @24.151s
└─run-user-1000-gvfs.mount @1min 14.724s
└─run-user-1000.mount @1min 3.167s
└─local-fs-pre.target @8.897s
└─systemd-tmpfiles-setup-dev.service @8.008s +8>
└─systemd-sysusers.service @6.679s +1.328s
└─systemd-remount-fs.service @6.303s +198ms
└─systemd-journald.socket @6.026s
└─system.slice @5.946s
└─-.slice @5.947s
请给我一个解决方案。