Bug 496007

Summary: kscreenlock does not unlock if left over night
Product: [KDE Neon] neon Reporter: Félim Whiteley <felim>
Component: generalAssignee: Neon Bugs <neon-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: carlosd.kde, jr, nate, neon-bugs-null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Félim Whiteley 2024-11-09 12:54:15 UTC 
Upgraded from KDE Neon 22.04 to 24.04 backend and it's broken unlocking the session if left over night. Shorter periods even of several hours it works fine. Over night I need to go to another virtual terminal; and use loginctl unlock-session

Operating System: KDE neon 6.2
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.8.0-48-generic (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 580 Series

Package: kscreenlocker
Version: 6.2.3-0zneon+24.04+noble+release+build10


See the following messages:

Nov 09 11:36:02 monolith kscreenlocker_greet[722401]: 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

Nov 09 11:36:09 monolith kscreenlocker_greet[722401]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/lockscreen/LockScreenUi.qml:280: TypeError: Property 'respond' of object length is not a function
Comment 1 Félim Whiteley 2024-11-10 19:32:12 UTC 
Setting an environment value in /etc/profile.d/kde_bug_fix.sh

#!/bin/bash
QV4_GC_TIMELIMIT=0
export QV4_GC_TIMELIMIT

Solved the issue for me.
Comment 2 Bug Janitor Service 2024-11-11 01:42:39 UTC 
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/245
Comment 3 Nate Graham 2024-11-12 14:40:39 UTC 

*** This bug has been marked as a duplicate of bug 494927 ***