| Summary: | Screen locker 'unable to unlock, use loginctl instead' randomly when system is locked | ||
|---|---|---|---|
| Product: | [Plasma] kscreenlocker | Reporter: | s1r51ckb01 |
| Component: | greeter | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | bhush94, bugseforuns, kde, KDE |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
Logfile
DMESG_LOG |
||
|
Description
s1r51ckb01
2019-03-08 14:42:46 UTC
Created attachment 118648 [details]
Logfile
Log in attachment
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? 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 Created attachment 118649 [details]
DMESG_LOG
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. Hi David, i run both commands but did not return errors New information was added with comment #6; changing status for inspection. 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 |