ZaWertun / fedora-copr-kde5

https://copr.fedorainfracloud.org/coprs/zawertun/kde/
18 stars 4 forks source link

Login takes considerably more time on 5.20.2-[3-4] #56

Closed aleasto closed 3 years ago

aleasto commented 4 years ago

On my system, in release 5.20.2-1 and all prior builds the splashscreen flashes a couple of times before i'm sent very quickly to my Desktop.

Starting with 5.20.2-3 and continuing in the hotfix build 5.20.2-4, after the splashscreen flashes it keeps spinning for ~10 more seconds, effectively doubling if not tripling the time to login

leosarra commented 4 years ago

I can confirm. Default login screen (Fedora) stops spinning after a couple of seconds then It remains for ~10 more seconds before disappearing.

architectlin commented 4 years ago

I can confirm, with me the same problem plasmashell 5.20.3

there was the problem before https://github.com/ZaWertun/fedora-copr-kde5/issues/33

ZaWertun commented 4 years ago

It's not easy to debug such problems. There is nice article from David Edmundson - http://blog.davidedmundson.co.uk/blog/plasma-startup/.

architectlin commented 4 years ago

It's not easy to debug such problems. There is nice article from David Edmundson - http://blog.davidedmundson.co.uk/blog/plasma-startup/.

I know this was the same last time:'(

ZaWertun commented 4 years ago

I could make package that installs modified systemd-bootchart and adds script that runs it on X11 start.

ZaWertun commented 4 years ago

Damn. It caused by my patch, when I'm trying to fix dbus-broker issue. New build: https://copr.fedorainfracloud.org/coprs/zawertun/kde/build/1767210/.

ZaWertun commented 4 years ago

But now after updating to 5.20.3 I have constant timeout before logging out (3-5 sec.).

leosarra commented 4 years ago

I can confirm that, after updating to the last build, the waiting time for logging in is back to normal. Thank you :+1:

aleasto commented 4 years ago

But now after updating to 5.20.3 I have constant timeout before logging out (3-5 sec.).

Stable 5.20.3 is out. Interestingly i have the same issue there.

aleasto commented 3 years ago

Oh well, I'll consider this fixed :)