Every time i log in to plasma, the splash screen is visible for exactly 30 seconds (i assume thats the timeout). However plasma is ready after a few seconds. $ top -b > log shows that there is barely any CPU activity after 8 seconds. $ when i log in via ssh and killall ksplashqml prematurely, plasma looks perfectly ready. I created a new user and logged in: same problem. On another (much slower) Computer with the same package versions, ksplashqml disappears after about 15 seconds, likely because plasma is ready... https://bugs.kde.org/show_bug.cgi?id=380495 sounded like it might be related, so i tried the patch: no change This has been going on for a while now.. perhaps since 5.12.0 Now i'm out of ideas where to look :/ What would, under normal circumstances, tell ksplashqml to quit?
>What would, under normal circumstances, tell ksplashqml to quit? Plasma signalling it's ready (along with some other modules) Can you include output of ~/.local/share/sddm/xorg-session.log after logging in.
Marking as needsinfo, please reset status to unconfirmed after attaching log
> Can you include output of ~/.local/share/sddm/xorg-session.log after logging in. I would, if there was something to include. $ ls -l ~/.local/share/sddm/xorg-session.log -rw------- 1 arek arek 0 Mär 13 14:29 /home/arek/.local/share/sddm/xorg-session.log same on my laptop btw. (where it's working properly) are there any other logs that could help?
just saw your comment about the status.. interpreting it as "set now".. I noticed one strange thing (althought my guess is it's probably unrelated): when i log in as myself, the rotating thingie below the plasma-icon disappers after ~8 sec. For the new user, it keeps rotating the full 30 sec until the end.
Bug no longer occurs in 5.12.5 :) As for formalaties: should I set the status to closed, or should that be done by the assignee/maintainer/whoever after some investigation into what might have fixed it? Are there any guidelines?
You can do it yourself. It's easy enough to re-open a bug. :) I'll do it for you this time since I'm already commenting here.