Я вижу что связано все с нетворкМенеджер, но это же работа с гуи Меню интернета.
name:~$ systemd-analyze blame
1min 1.044s NetworkManager-wait-online.service
32.291s docker.service
30.244s containerd.service
24.088s postgresql@14-main.service
22.709s networkd-dispatcher.service
22.706s snapd.service
20.455s ModemManager.service
19.092s udisks2.service
18.099s cups.service
11.019s ubuntu-system-adjustments.service
10.794s systemd-udev-settle.service
9.919s dev-sda1.device
8.309s accounts-daemon.service
7.958s systemd-journal-flush.service
4.609s systemd-udevd.service
4.524s power-profiles-daemon.service
4.361s polkit.service
4.342s avahi-daemon.service
4.331s bluetooth.service
4.326s NetworkManager.service
4.037s switcheroo-control.service
4.029s wpa_supplicant.service
4.024s thermald.service
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 @2min 3.401s
└─multi-user.target @2min 3.400s
└─docker.service @1min 31.107s +32.291s
└─network-online.target @1min 31.095s
└─network.target @30.045s
└─NetworkManager.service @25.718s +4.326s
└─dbus.service @25.707s
└─basic.target @25.496s
└─sockets.target @25.496s
└─snapd.socket @25.494s +1ms
└─sysinit.target @24.808s
└─snapd.apparmor.service @22.168s +2.639s
└─apparmor.service @20.568s +1.591s
└─local-fs.target @20.567s
└─run-user-1000-doc.mount @2min 2.050s
└─run-user-1000.mount @1min 25.922s
└─swap.target @16.753s
└─dev-disk-by\x2duuid-46a3f068\x2d42f7\x2d4f6a\>
└─dev-disk-by\x2duuid-46a3f068\x2d42f7\x2d4f6>
