Summary: | Kscreenlocker does not allow login once locked and causes coredumps | ||
---|---|---|---|
Product: | [Plasma] ksmserver | Reporter: | ruinz00 |
Component: | lockscreen | Assignee: | David Edmundson <kde> |
Status: | RESOLVED NOT A BUG | ||
Severity: | major | CC: | dbacc, mgraesslin, smyrman |
Priority: | NOR | ||
Version: | 5.2.90 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Systemd Journal extract |
Description
ruinz00
2015-04-24 04:29:21 UTC
Probably also happened to me. Got 74GiB of core dump files. Unfortunately they seam to be broken. Cannot unpack them. could you please provide some more information about the coredumps? I'm especially confused about the name "KScreenlocker" as there is no such binary called like that in the version you selected. There is a kscreenlocker_greet, though. Created attachment 92769 [details]
Systemd Journal extract
Core dump Systemd journal log (journalctl -xe)
Reproduced on Archlinux with KDE Plasma Workspace 5.3.0 (package plasma-workspace 5.3.0-3). The crash happens every time the correct password is given in the lock screen window - if the wrong password is given, the process doesn't die. (We see in the log that Vim dies as well, but that seams to be completely different issue.) PS! I can not log back in once the screen is locked:-) The only solution is the restart SDDM. SOLVED (for me at least) Both Vim and kscreenlocker_g where crashing due to outdated Intel microcode. Following the guide bellow solved my problem: https://wiki.archlinux.org/index.php/Microcode Thanks for giving an update on what solved the issue. Given that it's microcode I don't see anything we could do about it, thus the bug seems invalid to me. For future references: there was no need to restart the complete session. One can unlock using loginctl: 1. switch to tty and log in 2. loginctl unlock-sessions |