https://bugs.kde.org/show_bug.cgi?id=493145
--- Comment #22 from Adam Fontenot <adam.m.fontenot+...@gmail.com> --- I tried rebuilding kscreenlocker 6.1.5 and installed it. After rebooting my system, I was still able to reproduce the issue, so whatever caused it (in my case) must be coming from some other part of the Plasma 6.2 update. Here are my logs: Oct 17 14:30:00 athena kscreenlocker_greet[1550]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash Oct 17 14:30:03 athena kscreenlocker_greet[1550]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:128: TypeError: Property 'startAuthenticating' of object TypeError: Type error is not a function Oct 17 14:30:08 athena kscreenlocker_greet[1550]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 1.0015118079999998,-0.0004081919999999834,-0.0004081919999999834,0,0,1.00192,0,0,0,0,1.00192,0,0,0,0,1 is not a function Oct 17 14:30:28 athena kscreenlocker_greet[1550]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object 1.0015118079999998,-0.0004081919999999834,-0.0004081919999999834,0,0,1.00192,0,0,0,0,1.00192,0,0,0,0,1 is not a function That `startAuthenticating` failure seems pretty suspect, both the original reporter of this issue and I both see this in our logs. -- You are receiving this mail because: You are watching all bug changes.
