I have removed LightDM and have installed SDDM for KDE Plasma 5 (yeah, I took the plunge). For some reason, instead of only staying on this screen for about 1 to 2 seconds like it used on Xfce, it’s hanging around for about 35 seconds.
So, I’m wondering, did I flub up a file? Is there a config I confounded? Is there an SDDM setting that needs situating?
Inquiring minds want to know. What kinds of files would you need (or terminal info) to help me track this down?
TIA guys!
Hi @joekamprad. Thanks for the quick reply. This is the report. To my untrained eye, I don’t see anything that would make the system go from the clean function to the login screen in 36 seconds…but, I do stress; it’s my untrained eye!
10.632s man-db.service
4.653s updatedb.service
827ms upower.service
678ms lvm2-monitor.service
549ms dev-sda1.device
430ms systemd-logind.service
336ms udisks2.service
334ms systemd-tmpfiles-clean.service
297ms systemd-udevd.service
258ms systemd-journald.service
236ms ldconfig.service
93ms systemd-backlight@backlight:intel_backlight.service
92ms polkit.service
90ms systemd-udev-trigger.service
88ms systemd-journal-flush.service
61ms NetworkManager.service
53ms avahi-daemon.service
47ms user@1001.service
45ms systemd-tmpfiles-setup.service
41ms systemd-journal-catalog-update.service
28ms logrotate.service
28ms systemd-sysusers.service
25ms colord.service
25ms systemd-modules-load.service
15ms user-runtime-dir@1001.service
15ms systemd-sysctl.service
15ms systemd-tmpfiles-setup-dev.service
13ms dev-mqueue.mount
4.653s updatedb.service is the biggest but this is running periodically only…
this shows that the cuprit is not a systemd-service as times are o.k. 
next step boot log / journal:
journalctl -b -0 | curl -F 'f:1=<-' ix.io
https://endeavouros.com/docs/forum/how-to-include-systemlogs-in-your-post/
Maybe installing and enabling haveged could help here 
Just what I was about to suggest.
Hi. I have this installed already, but I have NO idea what it’s for, or how to use it.
I ran this code, and pasted the link into my browser. It gave me a lot of stuff. Is this something safe to share here on the forums? I can give the link here if you think it’s okay.
it may includes UUIDS of your harddrives, but i do not think this is a security risk…of you do not want to post them at here you can send me the link in a private message …
From the arch wiki:
The haveged project is an attempt to provide an easy-to-use, unpredictable random number generator based upon an adaptation of the HAVEGE algorithm. Haveged was created to remedy low-entropy conditions in the Linux random device that can occur under some workloads, especially on headless servers.
It’s a daemon/service running in the background so you simply have to start/enable it via systemctl. The delay maybe due to low entropy when starting SDDM.
I did the following: (Looks like it’s already running?)
ps -ef | grep haveged
USER 5294 4752 0 00:43 pts/2 00:00:00 grep haveged
It should look like this:
haveged 504 1 0 07:38 ? 00:00:00 /usr/bin/haveged --Foreground --verbose=1
csteinf+ 1712 1704 0 07:46 pts/2 00:00:00 grep --colour=auto haveged
Run
sudo systemctl status haveged
to get the status
and
sudo systemctl start haveged
sudo systemctl enable haveged
to start it right away and enable it on boot. Then try a reboot.
Maybe try a
sudo pacman -S haveged
beforehand.
Holy crap! @csteinforth! That worked with amazing results! I don’t even think Xfce came up this quickly from a reboot! Wow!
Look, guys…people talk a lot about this community. They talk about how friendly it is, and that’s very true! It’s also an amazing collection of human beings who have extensive information and can share it in a way that makes the neo-intermediates like me feel good about asking questions.
Thank you so much everyone who was involved!!!
I’m marking this “Solved”!
Glad this helped! It seems most noticeable to me with Plasma for some reason.
Does anyone know the exact reason? Heavy workload or something else?
Is it ok to necro bump this thread with an related issue of my own?
I followed this thread and my long start ups persist, using plasma and SDDM,
although I’m unsure how relevant these steps are now.
I think following the steps may have shortened the time down slightly, but is still very long.
When I,
When I,
1.195s dev-ttyS30.device
1.195s sys-devices-platform-serial8250-tty-ttyS30.device
1.194s dev-ttyS31.device
1.194s sys-devices-platform-serial8250-tty-ttyS31.device
1.194s dev-ttyS29.device
1.194s sys-devices-platform-serial8250-tty-ttyS29.device
1.193s sys-devices-platform-serial8250-tty-ttyS5.device
1.193s dev-ttyS5.device
1.192s dev-ttyS6.device
1.192s sys-devices-platform-serial8250-tty-ttyS6.device
1.192s sys-devices-platform-serial8250-tty-ttyS3.device
1.192s dev-ttyS3.device
1.192s sys-devices-platform-serial8250-tty-ttyS4.device
1.192s dev-ttyS4.device
1.192s dev-ttyS9.device
1.192s sys-devices-platform-serial8250-tty-ttyS9.device
1.192s dev-ttyS8.device
1.192s sys-devices-platform-serial8250-tty-ttyS8.device
1.191s sys-devices-platform-serial8250-tty-ttyS7.device
1.191s dev-ttyS7.device
1.164s dev-ttyS0.device
1.164s sys-devices-platform-serial8250-tty-ttyS0.device
1.164s sys-devices-platform-serial8250-tty-ttyS1.device
1.164s dev-ttyS1.device
1.164s sys-devices-platform-serial8250-tty-ttyS12.device
1.164s dev-ttyS12.device
1.163s dev-ttyS14.device
1.163s sys-devices-platform-serial8250-tty-ttyS14.device
1.163s sys-devices-platform-serial8250-tty-ttyS10.device
1.163s dev-ttyS10.device
1.162s sys-devices-platform-serial8250-tty-ttyS16.device
1.162s dev-ttyS16.device
1.162s dev-ttyS15.device
1.162s sys-devices-platform-serial8250-tty-ttyS15.device
1.162s dev-ttyS11.device
1.162s sys-devices-platform-serial8250-tty-ttyS11.device
1.162s dev-ttyS13.device
1.162s sys-devices-platform-serial8250-tty-ttyS13.device
1.162s sys-devices-platform-serial8250-tty-ttyS17.device
1.162s dev-ttyS17.device
1.162s dev-ttyS2.device
1.162s sys-devices-platform-serial8250-tty-ttyS2.device
1.162s sys-devices-platform-serial8250-tty-ttyS20.device
1.162s dev-ttyS20.device
1.161s dev-ttyS21.device
1.161s sys-devices-platform-serial8250-tty-ttyS21.device
1.161s dev-ttyS23.device
1.161s sys-devices-platform-serial8250-tty-ttyS23.device
1.161s dev-ttyS18.device
1.161s sys-devices-platform-serial8250-tty-ttyS18.device
1.161s sys-module-configfs.device
1.160s dev-ttyS22.device
1.160s sys-devices-platform-serial8250-tty-ttyS22.device
1.160s sys-devices-platform-serial8250-tty-ttyS26.device
1.160s dev-ttyS26.device
1.160s dev-ttyS19.device
1.160s sys-devices-platform-serial8250-tty-ttyS19.device
1.160s dev-ttyS27.device
1.160s sys-devices-platform-serial8250-tty-ttyS27.device
1.160s dev-ttyS25.device
1.160s sys-devices-platform-serial8250-tty-ttyS25.device
lines 1-61…skipping…
1.195s dev-ttyS30.device
1.195s sys-devices-platform-serial8250-tty-ttyS30.device
1.194s dev-ttyS31.device
1.194s sys-devices-platform-serial8250-tty-ttyS31.device
There is a few pages of that and then it relates to my disks,
being numerous entries with similar times as the TTY entries shown.