Created attachment 149781 [details] image SUMMARY The lock screen program is damaged and cannot be unlocked STEPS TO REPRODUCE OBSERVED RESULT Attachment image EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
```shell -` ystyle@Archlinux .o+` ---------------- `ooo/ OS: Arch Linux x86_64 `+oooo: Host: XPS 13 7390 `+oooooo: Kernel: 5.18.3-arch1-1 -+oooooo+: Uptime: 2 days, 7 hours, 5 mins `/:-:++oooo+: Packages: 1782 (pacman) `/++++/+++++++: Shell: zsh 5.9 `/++++++++++++++: DE: Plasma `/+++ooooooooooooo/` Theme: Breeze Dark [Plasma], Breeze [GTK2/3] ./ooosssso++osssssso+` Icons: breeze-dark [Plasma], breeze-dark [GTK2/3] .oossssso-````/ossssss+` Terminal: terminator -osssssso. :ssssssso. CPU: Intel i7-10710U (12) @ 4.700GHz :osssssss/ osssso+++. GPU: Intel Comet Lake UHD Graphics /ossssssss/ +ssssooo/- Memory: 13931MiB / 15693MiB `/ossssso+/:- -:/+osssso+- `+sso+:-` `.-/+oso: `++:. `-/+/ .` `/ ```
Please run `/usr/lib64/libexec/kscreenlocker_greet --testing` and paste the terminal output. Thanks!
ystyle@Archlinux ~ # LANG=en stat /usr/lib64/libexec/kscreenlocker_greet stat: cannot statx '/usr/lib64/libexec/kscreenlocker_greet': No such file or directory
Operating System: Arch Linux KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.95.0 Qt Version: 5.15.4 Kernel Version: 5.18.3-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10710U CPU @ 1.10GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics
Ok, that must not be where it lives on Arch Linux. You need to find the location of kscreenlocker_greet and run it with --testing, then paste the output here.
ystyle@Archlinux ~/Downloads LANG=en /usr/lib/kscreenlocker_greet --testing Locked at 1655880071 file:///usr/lib/qt/qml/QtQuick/Controls.2/ToolButton.qml: QML IconImage: Error decoding: file:///usr/share/icons/breeze-dark/actions/24/edit-copy.svg: Unsupported image format file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:8:1: module "QtQuick.VirtualKeyboard" is not installed file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:549: TypeError: Cannot read property 'longName' of undefined file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool
Thanks. This looks like the error: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:549: TypeError: Cannot read property 'longName' of undefined Code for it is: readonly property var layoutNames: keyboardLayout.layoutsList.length ? keyboardLayout.layoutsList[keyboardLayout.layout] : { shortName: "", displayName: "", longName: "" } This suggests that you have multiple keyboard layouts, but the active one wasn't defined in the data model somehow. Can you take a screenshot of the Layouts tab of your Keyboard page in System Settings?
Created attachment 150108 [details] keyboard layout
That warning will be a red herring. /usr/lib/kscreenlocker_greet --testing In the output there did you get a view with a password prompt or no window/the window closing?
Created attachment 150113 [details] lock window window is normal
and regular breaks like that every time? Can you run coredumpctl list kscreenlocker_greet ?
----------------- ✘ ystyle@Archlinux ~ coredumpctl list kscreenlocker_greet No coredumps found. ✘ ystyle@Archlinux ~ ------------------ I found a sentence missing in the text: This phenomenon is not common, there is a probability, I have encountered it about 4 times in a month or two
and it can use kde connect to unlock screen (in custom command)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!