|Summary:||Screen locker 'unable to unlock, use loginctl instead' randomly when system is locked|
|Component:||greeter||Assignee:||Plasma Bugs List <plasma-bugs>|
|Severity:||normal||CC:||bhush94, bugseforuns, kde, KDE|
|Latest Commit:||Version Fixed In:|
Description s1r51ckb01 2019-03-08 14:42:46 UTC
Similar to bug: 372275 385321 ------------ After about one hour of screen lock the message of unlocking via loginctl appears. SOFTWARE/OS VERSIONS OS: Arch Linux Kernel: x86_64 Linux 4.14.90-1-lts Uptime: 7h 22m Packages: 1341 Shell: zsh 5.7.1 Resolution: 3840x1080 DE: KDE 5.55.0 / Plasma 5.15.2 WM: KWin GTK Theme: Breeze [GTK2/3] Icon Theme: breeze Font: Noto Sans Regular CPU: Intel Core i7-4600U @ 4x 3.3GHz GPU: Mesa DRI Intel(R) Haswell Mobile RAM: 4229MiB / 7856MiB - - - - - - My setup is 2 monitor 1920x1080 (one with hdmi - one with mini display port) - - - - - - - Log:
Comment 1 s1r51ckb01 2019-03-08 14:44:05 UTC
Created attachment 118648 [details] Logfile Log in attachment
Comment 2 David Edmundson 2019-03-08 14:50:36 UTC
That will happen if kscreenlocker_greet has crashed. In any case, I'll need the crash dump of that. Your attached log is of plasmashell, a different process. Apparently in response to a screen changing?
Comment 3 s1r51ckb01 2019-03-08 14:55:05 UTC
Hi David, thanks for the response! I do not make any changes, the problem appears after about an hour of lock screen. You can direct me on which log to take? the only error trace I see with journalctl is the attached one
Comment 5 David Edmundson 2019-03-08 16:02:15 UTC
Run this /usr/lib64/libexec/kscreenlocker_greet --testing and see if it crashes. (that path might be subtly different on your distro, please look for that executable accordingly) If it does crash, hopefully we'll get a drkonqi crash dialog, failing that, please run gdb /usr/lib64/libexec/kscreenlocker_greet --testing and type "bt" when in the gdb prompt when it crashes.
Comment 6 s1r51ckb01 2019-03-11 09:06:33 UTC
Hi David, i run both commands but did not return errors
Comment 7 Christoph Feck 2019-03-24 12:22:47 UTC
New information was added with comment #6; changing status for inspection.
Comment 8 s1r51ckb01 2019-04-09 09:05:40 UTC
Hi guys, after having done some updates after the opening of this task, the described problem has not been repeated. I believe we can close it here