Since the update to plasma-login-manager 6.6.5  from 6.6.4, plasmalogin.service takes 4 secs more to load.

This is due to:

[Service]
ExecStartPre=-udevadm settle --timeout=10

https://invent.kde.org/plasma/plasma-lo … quests/130

From the MR, i understand this is specific to some hardware, but I never had issues with login before.

My question is what's the best way to handle this slower login now.

Do you guys think creating a systemd drop-in to be the correct way ? Maybe there is something else taking time to "settle" I can inspect to properly fix it indeed? How to dig into?

Thanks!

Last edited by kokoko3k (2026-06-06 12:12:25)

Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

Create a copy of /usr/lib/systemd/system/plasmalogin.service as /etc/systemd/system/plasmalogin.service, and modifiy it to your liking. This path has the highest priority on where systemd looks for service units. It won't be overwritten by the package manager.

Paths from highest to lowest priority (ignoring drop-in directories):

• /etc/systemd/system/

• /run/systemd/system/ (gone after power-off)

• /usr/lib/systemd/system/

https://wiki.archlinux.org/title/Systemd
https://man.archlinux.org/man/systemd.unit.5

Last edited by StarWolf3000 (2026-06-06 11:33:05)

Mainboard: GIGABYTE B550 AORUS ELITE V2 | CPU: Ryzen 7 5800X | RAM: 32 GB
GPU: GeForce RTX 4060 8 GB (580.119.02 proprietary) | Display: BenQ BL2405 1920x1080
Kernel: 6.18.8 stable | Boot Manager: GRUB2 | DE: KDE Plasma | Login Manager: SDDM | Compositor: KWin

Thanks.

After reading man systemd-udev-settle.service:
"Waiting for systemd-udev-settle.service usually slows boot significantly, because it means waiting for all unrelated events too."

I decided to make a service drop-in:
sudo systemctl edit plasmalogin.service --drop-in=noudevadmsettle

### Editing /etc/systemd/system/plasmalogin.service.d/noudevadmsettle.conf
### Anything between here and the comment below will become the contents of the drop-in file

[Service]
ExecStartPre=

### Edits below this comment will be discarded


### /usr/lib/systemd/system/plasmalogin.service
# [Unit]
# Description=Plasma Login Manager
# Documentation=man:plasmalogin(1) man:plasmalogin.conf(5)
# Conflicts=getty@tty1.service
# After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service systemd-logind.service
# PartOf=graphical.target
# StartLimitIntervalSec=30
# StartLimitBurst=2
#
# [Service]
# ExecStartPre=-udevadm settle --timeout=10
# ExecStart=/usr/bin/plasmalogin
# Restart=always
#
# [Install]
# Alias=display-manager.service

I hope plasma devs will find a better way to handle specific hardware issues.

Last edited by kokoko3k (2026-06-06 14:59:14)

Help me to improve ssh-rdp !
Retroarch User? Try my koko-aio shader !

Thank you very much! This has been bothering me as well and your solution worked perfectly!

I opened an upstream bug about it: https://bugs.kde.org/show_bug.cgi?id=523054

For me, it turned out that the culprit was my baddly written udev rule, but even when I fixed that, it still introduces 700 ms of delay. BTW: adding "udev.log_level=debug" to your boot parameters will allow you to inspect what is happening with "journalctl -b -u systemd-udevd".