Bug 325172

Summary: kscreenlocker startup is slow and also unlocking
Product: [Unmaintained] kscreensaver Reporter: Tommi Tervo <tommi.tervo>
Component: locker-qmlAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: jan, jeisom, konomikitten, mgraesslin
Priority: NOR    
Version: 4.11.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: full strace log (I changed passwd to some trivial one during this strace session)

Description Tommi Tervo 2013-09-22 11:57:44 UTC
kscreenlocker is very slow since upgrade to kde 4.11.0/1. 4.10.x series did not have this problem. I straced kscreenlocker_greet process startup and seems that it tries to find kscreenlocker_greet.png file over 18000 times during the start up without success.

Reproducible: Always
Comment 1 Tommi Tervo 2013-09-22 12:05:28 UTC
Created attachment 82458 [details]
full strace log (I changed passwd to some trivial one during this strace session)
Comment 2 Jonathan Isom 2013-12-03 20:01:07 UTC
I am getting this with 4.11.3, at least with regard to the login. It takes 20 seconds after hitting enter for the login to complete. The screensaver turns off, but I have a black screen for 20 seconds.  No input appears to be accepted during this time.
Comment 3 Konomi 2014-12-26 14:48:06 UTC
I have this problem too and I have for ages I was hoping it would eventually get fixed but it's been so long now. I have this problem on two seperate laptops the screenlock dialog is so so SO slow. You can watch the characters appear with 5 seconds delay between each letter as you type it on my netbook! Would someone address this already!?

Distro: Debian Testing
KDE Version: 4.14.2
Comment 4 Martin Flöser 2015-01-23 13:32:55 UTC
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.