Linux mi startuje 136 sekund.

Ahoj kluci. Ptala jsem se i jinde ale musím poprosit o pomoc i v mé nejoblíbenější poradně. Co mě trápí dnes. Mám PC HP AIO což většina kluků už ví. Disk NVME 500GB. Na něm dual boot. Windows 11 a Linux Mint 22.3 Zena, 64bit. Každý systém má půlku disku. Windows mě nezajímá. Trápí mě Linux. GRUB je nastavený tak, že počítač primárně bootuje do Linuxu. Úvodní logo a kolonka pro zadání hesla. Zadám heslo, enter a počítač mi najede za 136 sekund do desktopu. Naskočí mi desktop a poté se mi ještě 14 sekund točí kolečko. Zkoušela jsem

systemd-analyze blame

a dostala jsem

7.603s NetworkManager-wait-online.service
3.612s systemd-resolved.service
3.602s systemd-binfmt.service
3.583s systemd-timesyncd.service
3.505s snapd.apparmor.service
2.908s proc-sys-fs-binfmt_misc.mount
1.328s fwupd-refresh.service
1.219s fwupd.service
 952ms NetworkManager.service
 782ms postfix@-.service
 729ms systemd-backlight@backlight:amdgpu_bl1.service
 616ms snapd.seeded.service
 540ms snapd.service
 429ms blueman-mechanism.service
 330ms udisks2.service
 328ms dev-nvme0n1p5.device
 311ms user@1000.service
 293ms accounts-daemon.service
 256ms power-profiles-daemon.service
 252ms rsyslog.service
 252ms firewalld.service
 251ms polkit.service
 207ms gpu-manager.service
 198ms ubuntu-system-adjustments.service
 167ms systemd-udev-trigger.service
 166ms systemd-logind.service
 157ms avahi-daemon.service
 153ms apparmor.service
 153ms bluetooth.service
 148ms update-notifier-download.service
 136ms grub-common.service
 119ms dev-loop5.device
 118ms systemd-journald.service
 116ms dev-loop6.device
 116ms dev-loop13.device
 112ms lm-sensors.service
 112ms switcheroo-control.service
 110ms dev-loop7.device
 109ms dev-loop3.device
 109ms e2scrub_reap.service
 102ms dev-loop1.device
 101ms dev-loop4.device
 100ms dev-loop9.device
  98ms dev-loop2.device
  93ms systemd-journal-flush.service
  89ms dev-loop15.device
  89ms dev-loop11.device
  88ms dev-loop12.device
  87ms ModemManager.service
  84ms dev-loop14.device
  81ms dev-loop0.device
  78ms dbus.service
  77ms upower.service
  76ms dev-loop8.device
  76ms dev-loop10.device
  70ms systemd-udevd.service
  61ms lightdm.service
  58ms systemd-sysctl.service
  58ms keyboard-setup.service
  55ms wpa_supplicant.service
  53ms lvm2-monitor.service
  52ms grub-initrd-fallback.service
  51ms systemd-tmpfiles-clean.service
  50ms alsa-restore.service
  47ms snap-bare-5.mount
  46ms plymouth-quit-wait.service
  46ms snap-copilot\x2ddesktop-62.mount
  46ms systemd-tmpfiles-setup.service
  44ms snap-core18-2999.mount
  44ms systemd-modules-load.service
  42ms snap-core22-2339.mount
  41ms snap-core24-1349.mount
  40ms thermald.service
  39ms snap-core24-1499.mount
  38ms systemd-fsck@dev-disk-by\x2duuid-4A58\x2dF925.service
  37ms snap-gnome\x2d3\x2d28\x2d1804-198.mount
  34ms plymouth-start.service
  34ms snap-gnome\x2d46\x2d2404-153.mount
  32ms snap-gtk\x2dcommon\x2dthemes-1535.mount
  32ms boot-efi.mount
  31ms snap-mesa\x2d2404-1165.mount
  30ms dev-hugepages.mount
  29ms dev-mqueue.mount
  29ms sys-kernel-debug.mount
  28ms sys-kernel-tracing.mount
  28ms snap-picasa\x2dsnap-3.mount
  27ms packagekit.service
  27ms snap-prospect\x2dmail-79.mount
  26ms kerneloops.service
  25ms cups.service
  25ms snap-snapd-25935.mount
  23ms snap-twinux-62.mount
  22ms kmod-static-nodes.service
  22ms systemd-remount-fs.service
  21ms snap-wine\x2dplatform\x2d5\x2dstable-18.mount
  20ms modprobe@configfs.service
  20ms systemd-tmpfiles-setup-dev-early.service
  19ms snap-wine\x2dplatform\x2druntime-409.mount
  19ms systemd-update-utmp.service
  19ms modprobe@drm.service
  18ms plymouth-read-write.service
  17ms modprobe@fuse.service
  16ms flatpak-system-helper.service
  16ms console-setup.service
  16ms rtkit-daemon.service
  15ms systemd-update-utmp-runlevel.service
  14ms finalrd.service
  12ms systemd-tmpfiles-setup-dev.service
  12ms systemd-random-seed.service
  11ms snapd.socket
  11ms modprobe@efi_pstore.service
  11ms user-runtime-dir@1000.service
  10ms modprobe@loop.service
  10ms ufw.service
  10ms systemd-user-sessions.service
  10ms casper-md5check.service
   9ms sys-fs-fuse-connections.mount
   8ms sys-kernel-config.mount
   8ms swapfile.swap
   7ms openvpn.service
   7ms systemd-rfkill.service
   5ms modprobe@dm_mod.service
   2ms setvtrgb.service
   2ms postfix.service
  30us blk-availability.service

Z toho nejsem vůbec moudrá. Chtěla jsem najít kde dochází k tomu velkému zpoždění a brzdě. Po zadání

systemd-analyze critical-chain

jsem dostala

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 @14.426s
└─multi-user.target @14.426s
  └─postfix.service @14.423s +2ms
    └─postfix@-.service @13.624s +782ms
      └─network-online.target @13.597s
        └─NetworkManager-wait-online.service @5.993s +7.603s
          └─NetworkManager.service @5.026s +952ms
            └─network-pre.target @5.021s
              └─firewalld.service @4.768s +252ms
                └─polkit.service @4.508s +251ms
                  └─basic.target @4.476s
                    └─sockets.target @4.476s
                      └─snapd.socket @4.464s +11ms
                        └─sysinit.target @4.459s
                          └─systemd-backlight@backlight:amdgpu_bl1.service @4.9>
                            └─system-systemd\x2dbacklight.slice @4.902s
                              └─system.slice @297ms
                                └─-.slice @297ms

A z toho se mi už motá hlava.
Nevím co s tím a nevím co z těch nejdelších časů mohu zakázat/omezit/vypnout/odstranit prioritu.
Dokážete mi někdo pls poradit co s tím? Děkuji.