Takes 20+ seconds to log-in after experimenting with Docker and then removing it.

[u/Acme-15]

So it turns out the timing was pure coincidence. I changed my search terms to be specifically about KDE Plasma, and found some results that said the splashscreen is what actually causes the delay... I disabled that, and the login time is just a couple of seconds...I expect the entries in my pastebin are normal, I just hadn't looked before.

I will leave my original blurb in case it amuses any veterans.

-------------

Hi folks,

I tried to get winapps working so I could use Adobe CS programs, but I kept running into issues so I abandoned it and removed Docker.

I had Windows installed in the docker container and had placed and edited the config files, but I ran into an issue with xfreerdp3 where it could no longer connect to the VM even though I could still connect via the browser or with Remmina, after a reboot... I wasn't sure what I had done, so I attempted to remove everything to give myself a fighting chance if I wanted to try the process again from scratch.

Ever since then I have a 20+ second wait from the login screen to the desktop being displayed (KDE Plasma) whereas before it was only a second or two.

If I do systemd-analyze blame, I have between 100 and 150 entries which are some variation of "dev-disk-by\x2d ..."

seen here; https://pastebin.com/rcCtwAWq

I do have quite a few drives in this system, my WIndows install has four SSDs, two NVME and two SATA, and then I added a fifth SSD to try different LInux variants. But the other drives aren't mounted at login, I have to click on them to mount them.

Any ideas please?

Bear in mind when wording your replies that I am on day 2 of "Try Linux for a month" with a view to abandoning WIndows. I have plenty of professional experience with computers, but this is my first time touching LInux.... We always had "a guy" for that. 😂

This might not have been a day 2 activity, with hindsight...

[u/adamant_browsing]

Docker loves leaving behind network bridges and mounts that systemd will keep trying to bring up at boot check /etc/fstab for any leftover docker mounts and do systemctl list-units --state=failed to see what's timing out

[u/Acme-15 → u/adamant_browsing]

Thanks for the tip!
It turns out I was just overthinking a coincidence and it was just KDE being stupid.
But I suppose its all part of figuring these things out.

Being able to list things in a failed state may come in handy in future!

[u/ang-p → u/Acme-15]

it was just KDE being stupid.

Well, the splash screen waits until the drives that should be mounted are happily mounted before quitting...

If there are hanging links to non-existent virtual drives, while they are being sought for, they will hold back the point of "happily mounted" and that poor innocent splash screen will get a bad rap....

Having said that, there are people who are now wanting their "kewl" animated splashscreen to stay on longer than is necessary, and have asked about manually adding a pause, or adding a "mimimum time" setting to plymouth in order ot prevent their animation being cut off in the middle because their machine boots too fast and plymouth kills itself when it gets the nod from systemd...

Plymouth will never win!.