Hi!
It takes KDE Neon 24 seconds to boot. Debian does it in 8 seconds. This is on the same computer and both installs is on SSD's.

KDE Neon:
http://www.bronsaldersvagen.se/Eazy/boot_Neon.svg

Debian Buster:
http://www.bronsaldersvagen.se/Eazy/boot_Debian.svg

This is no criticism, I just wonder why KDE Neon (Ubuntu) is slower?

KDE Neon is a perfect distribution for me with low memory (RAM) usage and a setup that meets the basic needs (to avoid installing many applications I won't use by default).

But... the problem is that KDE Neon is too cumbersome to boot (slow boot and shutdown times). This situation is very annoying. I hope there's a cure for that as soon as possible.

Have a good day, have fun.

Maybe irrelevant with your case, but mine also used to boot so long after upgrading from Xenial to Bionic. Turns out it was due to something about outdated initramfs' resume file for swap uuid (https://askubuntu.com/a/1034952/847385). The solution mentioned in that answer fixed it for me (more details about the issue can be seen in the linked bug reports). Booting time has gone down to less than 10s ever since (that includes typing in my password after the prompt appears to finally seeing the desktop interface).

bobbywibowo wrote:Maybe irrelevant with your case, but mine also used to boot so long after upgrading from Xenial to Bionic. Turns out it was due to something about outdated initramfs' resume file for swap uuid (https://askubuntu.com/a/1034952/847385). The solution mentioned in that answer fixed it for me (more details about the issue can be seen in the linked bug reports). Booting time has gone down to less than 10s ever since (that includes typing in my password after the prompt appears to finally seeing the desktop interface).

Hello,

First of all thank you for the suggestion. /etc/initramfs-tools/conf.d/resume does not have this file ...

KDE and KDE neon developers should address this issue and produce solutions.

Have a good day, have fun.

Hi,
Can you post the output of the following command in the blog?
It would be useful in order to compare both Debian and KDE Neon, maybe they have differences on the services managed at the startup.
I noticed you use systemd-analyze plot to show the results.

jochoa@jochoapc:~$ systemd-analyze blame
55.463s apt-daily.service
17.983s dev-sda1.device
15.722s systemd-journal-flush.service
12.494s lvm2-monitor.service
12.210s systemd-tmpfiles-setup-dev.service
6.349s NetworkManager-wait-online.service
4.562s snapd.service
4.179s NetworkManager.service
4.015s udisks2.service
3.468s accounts-daemon.service
3.392s ModemManager.service
2.870s networkd-dispatcher.service
2.595s thermald.service
1.969s dev-loop2.device
1.639s motd-news.service
1.616s avahi-daemon.service
1.552s keyboard-setup.service
1.322s apt-daily-upgrade.service
1.246s systemd-modules-load.service
1.196s systemd-sysctl.service
1.191s resolvconf.service
1.153s gpu-manager.service
1.137s dev-loop0.device
1.129s dev-loop1.device
1.109s dev-loop3.device
1.101s fstrim.service
1.100s dev-loop5.device

Regards,

Hello,

hsnnsnc@hsnnsnc-MS-7751:~$ systemd-analyze blame
22.603s dev-sda2.device
21.241s systemd-journal-flush.service
16.156s lvm2-monitor.service
15.664s systemd-sysctl.service
13.079s NetworkManager-wait-online.service
12.901s systemd-udevd.service
3.792s NetworkManager.service
3.493s snapd.service
3.474s keyboard-setup.service
3.151s udisks2.service
3.101s vboxdrv.service
3.039s systemd-tmpfiles-setup-dev.service
2.913s ModemManager.service
2.844s accounts-daemon.service
2.689s networkd-dispatcher.service
2.071s gpu-manager.service
1.705s dev-loop2.device
1.692s dev-loop3.device
1.665s dev-loop0.device
1.521s systemd-modules-load.service
1.350s avahi-daemon.service
1.301s dev-loop1.device
1.269s thermald.service
899ms polkit.service
851ms wpa_supplicant.service
839ms rsyslog.service
756ms snap-kde\x2dframeworks\x2d5-27.mount
731ms dev-mqueue.mount
731ms dev-hugepages.mount
708ms apparmor.service
666ms systemd-remount-fs.service
635ms sys-kernel-debug.mount
552ms kmod-static-nodes.service
545ms systemd-tmpfiles-setup.service
545ms swapfile.swap
447ms grub-common.service
372ms blk-availability.service
367ms packagekit.service
262ms systemd-journald.service
254ms systemd-resolved.service
236ms plymouth-read-write.service
227ms systemd-logind.service
168ms snap-core-6034.mount
165ms systemd-udev-trigger.service
151ms systemd-timesyncd.service
148ms systemd-random-seed.service
137ms systemd-update-utmp.service
131ms ufw.service
124ms nvidia-persistenced.service
116ms upower.service
90ms setvtrgb.service
63ms systemd-fsck@dev-disk-by\x2duuid-E799\x2dDB28.service
60ms virtualbox.service
54ms snap-core-5897.mount
41ms user@1000.service
39ms plymouth-quit.service
39ms plymouth-quit-wait.service
34ms boot-efi.mount
25ms snapd.socket
17ms snapd.seeded.service
16ms snap-core-6130.mount
13ms plymouth-start.service
9ms alsa-restore.service
4ms systemd-update-utmp-runlevel.service
4ms ureadahead-stop.service
4ms console-setup.service
3ms pppd-dns.service
2ms vboxautostart-service.service
2ms rtkit-daemon.service
2ms vboxweb-service.service
2ms vboxballoonctrl-service.service
2ms systemd-user-sessions.service
2ms sddm.service
1ms sys-kernel-config.mount
1ms sys-fs-fuse-connections.mount

Have a good day, have fun.

Not sure how much of an issue this is. It would be subjective to hardware. On a Xiaomi Notebook (12.5 Air with Core M3) it boots in about 8 to 10 seconds. On my Ryzen desktop and Lenovo Y410p it boots in about 12 seconds. But both of those throw a post and logo screen into the mix.