When the default splash screen "Breeze" is chosen in systemsettings and you login the progress bar in the splash screen loads to 100% and then freezes for ~20-30 seconds before you can see the desktop. In the error log when starting KDE plasma 5 from the console you can see: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/splash/Splash.qml: 50:13: QML Image: Binding loop detected for property „sourceSize.width“. Removing the line does not help. Setting the splash screen to "None" solves this issue. Reproducible: Always Steps to Reproduce: 1. Select "Breeze" splash screen (which is default) 2. Logout. 3. Login or start it with startkde Actual Results: Hangs at 100%. Expected Results: Splash screen should disappear when progress bar reached 100%.
Plasmashell 5.6.4 ArchLinux - 4.5.4-1-ARCH Its happening here too... But, i no longer have to wait, i just switch to TTY 2 and back again to TTY 1 ( Can be different, depending on system or installation ), and instantly resume.
plasmashell 5.6.5 first boot, seems fixed
No change on my system after the update. KDE Plasma 5.6.5, KDE Frameworks 5.22.0, Qt 5.6.1 on Arch Linux;
(In reply to Natenom from comment #3) > No change on my system after the update. > KDE Plasma 5.6.5, KDE Frameworks 5.22.0, Qt 5.6.1 on Arch Linux; First boot after update went ok ( no idea why ), and after that same error.
i have the same problem. Please get this fixed this is an annoying bug
This happens on my system as well, but the loading bar doesn't freeze; it stops at different points after ~70% and takes a total of 30 seconds to enter the desktop. I would also add that it happens with all splash screen themes. Selecting 'None' resolves this as previously mentioned. Distro: KaOS (2017) x64 with Linux kernel v4.9.12-1 KDE Plasma v5.9.4 KDE Frameworks: v5.32.0 Qt Version: 5.8.0
ksplash will close when all startup services have reported they're ready. It then gives up and times out after 30 seconds. If you hit this it means one of your important services is not starting up properly. If that's the case, that needs identifying and fixing. @Erikton Konomi you're almost certainly hitting the ksmserver bug that came in 5.9.5, which is fixed in a patch release out yesterday (5.9.5.1) Older ones are an old Plasma bug which is also fixed. If you still have this with 5.9.5.1 or newer please attach a dbus log of your startup (just add "dbus-monitor > ~/some.log &" to the top of the startkde file) and we can see what's actually broken.