SUMMARY Currently KSplash is contraproductive. It would make sense to use it for covering the loading tiles and all, but it just prolongs the process. OBSERVED RESULT Ksplash loads and the elements dont load until its finished. This makes it slower and has no use. EXPECTED RESULT Ksplash could be really useful. There are nice screens and displaying it as an overlay while the elements "settle down" (sometimes moving quite a lot at start) would be very nice. SOFTWARE/OS VERSIONS Fedora Kinoite 37 KDE 5.27.3 KDE Frameworks: 5.104.0 Qt: 5.15.8
KSplash's reason for existing is to hide the desktop while UI elements like the panel and desktop icons load, so you don't have the experience of seeing Plasma UI elements load one at a time (first the wallpaper, then the desktop icons, then the panel, then the panel contents, etc). Are you saying this isn't working for you, and Plasma only starts loading its individual UI elements *after* KSplash has disappeared? Any chance you can make a phone recording of the issue happening?
https://cloud.uol.de/s/nxdBnreXkXjpiBS I tried it. I removed all the autostart apps too, and without ksplash the loading of the UI elements is a bit slower than what I saw AFTER ksplash, but in total its faster. So KSplash seems to slow down the loading, even though it doesnt seem it actually just starts after ksplash finished.
edit: yes it seems it really just starts after ksplash finished. I removed some big autostart apps, thats why the performance increase I suppose
There is discussion about removing it, but this isn't a bug per-se. Everything works as intended.
To me it looks like the screen recording supports the originally reported bug, that Plasma's UI elements only start appearing after KSplash has disappeared, defeating the point of its existence. So it seems that things are in fact not working as intended; re-opening.
*** This bug has been marked as a duplicate of bug 357170 ***