Bug 435233 - Unable to authenticate after screen lock
Summary: Unable to authenticate after screen lock
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.18.7
Platform: Neon Linux
: VHI critical
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: regression
: 438498 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-04-01 20:18 UTC by David Fernández
Modified: 2021-07-07 12:34 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Fernández 2021-04-01 20:18:47 UTC
SUMMARY
Unable to authenticate after screen lock

STEPS TO REPRODUCE
1. Boot system normally. After login, use the desktop as usual
2. Lock desktop with Ctrl+Alt+L / "Lock screen" 
3. Now, you can't login again. No login window...

OBSERVED RESULT
Black screen without login window to return to desktop 

EXPECTED RESULT
Login window to unlock the screen

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: KDE neon Plasma LTS 5.18
(available in About System)
KDE Plasma Version: 5.18.7
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
All was ok in previous version (5.18.6), but after last update to the 5.18.7 version (March 30, 2021) the described problem appeared.
Comment 1 Nate Graham 2021-04-02 00:18:19 UTC
Oh dear.

Dollars to donuts it was https://invent.kde.org/plasma/plasma-workspace/commit/13057013d55ae19e76d29b9edc96510e52da2a7a or https://invent.kde.org/plasma/plasma-workspace/commit/697b103f5fad5b40b207eabcbce162d6672f5d91.

Can you please run `/usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing` in a terminal window and attach the full text output? it will tell us the exact error.
Comment 2 David Fernández 2021-04-02 05:59:33 UTC
Thanks for the quick response.

After running the suggested command I get the same black screen without the identification window, plus the following information:

$ /usr/lib/x86_64-linux-gnu/libexec/kscreenlocker_greet --testing
OpenGL vendor string:                   Intel
OpenGL renderer string:                 Mesa Intel(R) HD Graphics 530 (SKL GT2)
OpenGL version string:                  4.6 (Compatibility Profile) Mesa 20.2.6
OpenGL shading language version string: 4.60
Driver:                                 Intel
GPU class:                              Unknown
OpenGL version:                         4.6
GLSL version:                           4.60
Mesa version:                           20.2.6
Linux kernel version:                   5.4
Requires strict binding:                yes
GLSL shaders:                           yes
Texture NPOT support:                   yes
Virtual Machine:                        no
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 1617342572
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml:233:26: Type MainBlock unavailable
file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/MainBlock.qml:73:13: Cannot assign to non-existent property "cursorVisible"

-----------------------------------------------------------

The same thing happens to me on another computer with different specifications but with the same version of KDE neon and also upgraded to 5.18.7
Comment 3 Nate Graham 2021-04-03 04:44:05 UTC
I took a day off today but will make it my top priority to investigate and fix this tomorrow. So sorry for the regression, especially in the LTS release! :)
Comment 4 David Fernández 2021-04-03 12:29:41 UTC
Thank you in advance for your dedication and effort.
Comment 5 Bug Janitor Service 2021-04-03 15:05:29 UTC
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/768
Comment 6 Nate Graham 2021-04-03 15:19:43 UTC
Git commit c4a3a4e5b974fb309a6da61252b2b830d2d90683 by Nate Graham.
Committed on 03/04/2021 at 14:53.
Pushed by davidedmundson into branch 'Plasma/5.18'.

Revert "[lookandfeel] Fix wake existing screensaver mode with key presses"

This reverts commit 13057013d55ae19e76d29b9edc96510e52da2a7a.

That commit set the cursorVisible: propety to true. However that
property only exists in the QtQuickControls 2 TextField, not the QQC1
version. We ported the lock screen to PlasmaComponents3 (which
internally uses QQC2) after Plasma 5.18, meaning that in the LTS
version, we still have a QQC1 TextField so this property does not exist.
Trying to set it causes a runtime error and breaks the lock screen.
FIXED-IN: 5.18.7.1

M  +3    -0    lookandfeel/contents/lockscreen/LockScreenUi.qml
M  +0    -6    lookandfeel/contents/lockscreen/MainBlock.qml

https://invent.kde.org/plasma/plasma-workspace/commit/c4a3a4e5b974fb309a6da61252b2b830d2d90683
Comment 7 David Fernández 2021-04-04 06:01:56 UTC
Perfect. I just updated the system and the bug is gone ;-)
Very good job.
Best regards.
Comment 8 Nate Graham 2021-04-05 01:02:07 UTC
Phew, glad to hear it! So sorry that this happened in the first place.
Comment 9 Nate Graham 2021-06-15 23:00:19 UTC
*** Bug 438498 has been marked as a duplicate of this bug. ***
Comment 10 Nate Graham 2021-07-07 12:34:07 UTC
*** Bug 438498 has been marked as a duplicate of this bug. ***