Why does Debian take a long time to load?

Question

linux

Hello.

I have Debian 10.3 + KDE Plasma installed.
When I start the computer and after going through the GRUB bootloader, I have the KDE logo on the screen for 29 seconds, and only then the desktop appears.
At the very beginning, it took 17-19 seconds to fully boot the computer (SSD). Now only the last splash screen takes 29 seconds.

When I run the command in the console, systemd-analyzeI get the following output:

systemd-analyze

Startup finished in 2.370s (kernel) + 1.257s (userspace) = 3.627s 
graphical.target reached after 1.251s in userspace

When I run the command, systemd-analyze blameI get:

systemd-analyze blame

620ms systemd-logind.service
258ms apt-daily.service
220ms upower.service
167ms dev-nvme0n1p2.device
132ms systemd-timesyncd.service
80ms udisks2.service
77ms ModemManager.service
69ms systemd-journald.service
62ms accounts-daemon.service
50ms [email protected]\x2duuid-BFF8\x2d9E25.service
49ms keyboard-setup.service
47ms NetworkManager.service
40ms avahi-daemon.service
40ms systemd-udev-trigger.service
40ms apparmor.service
37ms systemd-tmpfiles-clean.service
33ms networking.service
33ms [email protected]
33ms rsyslog.service
31ms alsa-restore.service
31ms wpa_supplicant.service
30ms pppd-dns.service
25ms systemd-tmpfiles-setup.service
24ms systemd-modules-load.service
23ms plymouth-quit-wait.service
22ms systemd-udevd.service
22ms dev-disk-by\x2duuid-a4f706b9\x2d9a28\x2d4c2d\x2d866d\x2de45c266da4e4.swap
21ms plymouth-quit.service
20ms plymouth-start.service
18ms plymouth-read-write.service
15ms boot-efi.mount
10ms systemd-journal-flush.service
9ms polkit.service
9ms systemd-user-sessions.service
7ms systemd-tmpfiles-setup-dev.service
7ms [email protected]
7ms systemd-remount-fs.service
7ms systemd-update-utmp.service
6ms console-setup.service
6ms systemd-sysusers.service
5ms systemd-update-utmp-runlevel.service
5ms dev-hugepages.mount
4ms systemd-sysctl.service
4ms kmod-static-nodes.service
3ms sddm.service
3ms systemd-random-seed.service
3ms rtkit-daemon.service
3ms dev-mqueue.mount
2ms ifupdown-pre.service
2ms sys-kernel-debug.mount

When running the commandsystemd-analyze critical-chain

systemd-analyze critical-chain

graphical.target @1.251s
└─sddm.service @1.247s +3ms
  └─systemd-logind.service @621ms +620ms
    └─basic.target @615ms
      └─sockets.target @615ms
        └─avahi-daemon.socket @615ms
          └─sysinit.target @614ms
            └─systemd-timesyncd.service @481ms +132ms
              └─systemd-tmpfiles-setup.service @455ms +25ms
                └─local-fs.target @455ms
                  └─boot-efi.mount @439ms +15ms
                    └─[email protected]\x2duuid-BFF8\x2d9E25.service @388ms +50ms
                      └─dev-disk-by\x2duuid-BFF8\x2d9E25.device @380ms

In general, long loading began to occur after I slightly edited the panel on the desktop in KDE (I already sort of returned everything back) and after I tried to install new fonts through the .deb package: ttf-mscorefonts-installer_3.7_all.deb , with using the Discover package manager built into KDE.
When I installed this package, the package manager (Discover) hung on the installation and neither canceled the installation nor closed the window. I then turned off the power and it seems that after that Linux began to boot for a long time.

How to solve this problem?

Answer 1

I would try reinstalling KDE packages