Bug 426902 - Unlock fails even with correct password
Summary: Unlock fails even with correct password
Status: RESOLVED DUPLICATE of bug 428613
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Manjaro Linux
: VHI critical
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 427254 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-09-23 13:23 UTC by medin
Modified: 2020-12-05 23:16 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Unlock fails (1.69 MB, application/x-xz)
2020-09-23 14:21 UTC, medin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description medin 2020-09-23 13:23:40 UTC
If I lock my session, then take a piece of cloth and wipe the keyboard, in this action every key is almost pressed, so after finishing and trying to type the correct password the unlocking fails, the only possible solution is press hard on power off button to force shutdown.

This process is always reproducible on my machine, I don't know how to record a locked screen (even if recorded there is no way to save the video because it's impossible to unlock the session) or where to find the log of unlocking process to investigate this weird behavior.

Operating System: Manjaro Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.4.64-1-MANJARO
OS Type: 64-bit
Comment 1 medin 2020-09-23 14:21:06 UTC
I succeeded to create a record for lock screen with OBS. See attached video for more info.
Comment 2 medin 2020-09-23 14:21:55 UTC
Created attachment 131884 [details]
Unlock fails
Comment 3 David Edmundson 2020-09-23 15:10:03 UTC
In the video the virtual keyboard appears a few times, is that relevant?

In terms of logs, best bet is to invoke the screen locker in a windowed mode.

/usr/lib64/libexec/kscreenlocker_greet --testing
Comment 4 medin 2020-09-23 15:37:01 UTC
(In reply to David Edmundson from comment #3)
> In the video the virtual keyboard appears a few times, is that relevant?

No, my movements over the keyboard are random and probably the virtual keyboard appearance is due to pressing tab and space keys multiple times, but the goal of the video is at the end where the unlock fails and there is no way to recover my work in the locked session.
Comment 5 medin 2020-09-23 15:45:22 UTC
(In reply to David Edmundson from comment #3)

> In terms of logs, best bet is to invoke the screen locker in a windowed mode.
> 
> /usr/lib64/libexec/kscreenlocker_greet --testing


This the log I get in terminal :

file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreen.qml:52:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Locked at 1600875637
UdevQt: unable to create udev monitor connection
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/lib/qt/qml/QtQuick/Controls/Styles/Plasma/ToolButtonStyle.qml:209:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MainBlock.qml:88:13: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:64:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:41:5: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/SessionManagementScreen.qml:64:5: Unable to assign [undefined] to int
file:///usr/lib/qt/qml/org/kde/plasma/components/Button.qml:52: ReferenceError: PlasmaCore is not defined
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/ActionButton.qml:33:5: Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/KeyboardLayoutButton.qml:29:5: Unable to assign [undefined] to int
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/Battery.qml:48:9: Unable to assign [undefined] to double
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserDelegate.qml:41:5: Unable to assign [undefined] to int
qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:407:126: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:126: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:408:385: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:409:125: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:410:124: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:125: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:371: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:411:619: Could not add child element to parent element because the types are incorrect.
Authentication failure
Authentication failure
Authentication failure
Authentication failure
Authentication failure
Comment 6 medin 2020-09-23 15:48:35 UTC
kf.config.core: couldn't lock local file
Comment 7 Patrick Silva 2020-10-14 20:42:52 UTC
*** Bug 427254 has been marked as a duplicate of this bug. ***
Comment 8 Patrick Silva 2020-10-14 20:44:03 UTC
I noticed this problem on neon unstable today.
Then I typed my pasword with the virtual keyboard and my screen was unlocked as expected.
Comment 9 hchain 2020-10-21 08:24:27 UTC
Reproduced (no virtual keyboard)
Comment 10 hchain 2020-10-21 08:29:43 UTC
Qt: Session management error: Could not open network socket
Locked at 1603268712
file:///usr/lib/qt/qml/QtQuick/Controls.2/ToolButton.qml: QML IconImage: Error decoding: file:///usr/share/icons/breeze-dark/actions/22/edit-copy.svg: Unsupported image format
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/osd/OsdItem.qml:50:9: Unable to assign [undefined] to double
file:///usr/lib/qt/qml/org/kde/plasma/components.3/TextField.qml:36: ReferenceError: textField is not defined
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
file:///usr/lib/qt/qml/org/kde/plasma/components.3/TextField.qml:36: ReferenceError: textField is not defined
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/osd/OsdItem.qml:50:9: Unable to assign [undefined] to double
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
QXcbClipboard: SelectionRequest too old
Authentication failure
Comment 11 Ongun Kanat 2020-11-05 00:28:29 UTC
Archlinux introduced new security limitations which blocks session for 15 mins after 3 consequent failed attempts. Probably Manjaro copied the pam package too. Edit /etc/security/faillock.conf to disable this or increase the number of failed attempts before blocking.
Comment 12 Nate Graham 2020-11-05 02:00:29 UTC
That seems like it. Go complain to the Arch packagers I guess. Communicating this to the user better is tracked with Bug 428613.
Comment 13 hchain 2020-11-28 09:35:06 UTC
I don't think this is it. It fails to unlock even on the first (correct) attempt. Also I only get the issue with master, when I switch back to 5.20.3 the problem disappears. I'm also using Arch Linux however
Comment 14 Nate Graham 2020-11-28 15:54:33 UTC
Well that's bad. :(
Comment 15 David Edmundson 2020-12-05 23:16:11 UTC
>I don't think this is it

If it's not, please get some more info and reopen.

All the info we have an the first reports are definitely this.

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