SUMMARY When splash screen is disabled, plasma starts however it takes long time before it starts applications in autostart, powerdevil and possibly others. STEPS TO REPRODUCE 1. Disable splash screen 2. Restart plasma session OBSERVED RESULT Applications in autostart, powerdevil and possibly others take long time to start. plasma-ksmserver.service prints following: led 30 16:58:22 NB0656 systemd[1645]: Starting KDE Session Management Server... led 30 16:58:22 NB0656 ksmserver[1738]: Qt: Session management error: networkIdsList argument is NULL led 30 16:58:23 NB0656 ksmserver[1738]: QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.12' led 30 16:59:13 NB0656 qdbus[1845]: Cannot find 'org.kde.KSplash.setStage' in object /KSplash at org.kde.KSplash led 30 16:59:13 NB0656 systemd[1645]: Started KDE Session Management Server. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Might be also caused by some packaging/configuration problem as I am using this unofficial COPR repository https://copr.fedorainfracloud.org/coprs/mkyral/plasma-unstable
I did experience the same thing but only after enabling systemd startup: kwriteconfig5 --file startkderc --group General --key systemdBoot true additionaly powerdevil stopped intercepring power button events so pressing the power button just shut down my laptop instead of displaying the logout dialog. Enabling splash fixed the deylayed autostart but powerdevil still didn't work as expected so I had to go back to the non systemd startup: kwriteconfig5 --file startkderc --group General --key systemdBoot false Operating System: Arch Linux KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620
Cannot reproduce. Are you able to reproduce this issue in Plasma 5.25 or later?
This issue is no longer there for me.
OK great! Thanks for the info.