Bug 460353

Summary: Password prompt to unlock screen becomes unresponsive, have to kill Xorg or reboot
Product: [Plasma] kscreenlocker Reporter: php4fan
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: critical CC: bhush94, nate
Priority: VHI    
Version: 5.25.5   
Target Milestone: ---   
Platform: Manjaro   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description php4fan 2022-10-13 11:02:24 UTC
SUMMARY

I use my laptop usually with an external screen connected as the only screen (with the laptop lid closed and an external keyboard and mouse), mention this just in case it's relevant.

STEPS TO REPRODUCE
1. Leave my computer unattended for several minutes
2. The screen automatically locks and later turns off
3. shake the mouse > the screens turns on and the password prompt show up
4. Type in the password to unlock and resume working

OBSERVED RESULT

Most of the times this all works as expected, but from time to time, the password prompt goes completely berserk, becomes unresponsive, the screen flickers, and it's impossible to enter the password and unlock.

Sometimes the password prompt doesn't even show up, only the background screen (then some random sequence of clicking, shaking the mouse, hammering the keyboard, sometimes makes it show up, but still unresponsive and not working).

Sometimes, not always, by just switching to a virtual tty and back (e.g. Ctrl+Alt+F2, Ctrl+Alt+F1) just magically makes it work.
When it does not, it still usually causes all the characters that you had been hitting on the keyboard that hadn't shown up, to show up in the input box (obviously as bullets, not the actual characters).

When switching to the tty, I tried logging in and running some commands. Top doesn't show any unusually high CPU or memory consumption by any process.

The only thing that I was able to do to be able to resume working was to kill xorg, but obviously I lose the session and any unsaved work, it's just the same as rebooting, it's not a workaround.

Before that, I  tried killing the "plashashell" process and that didn't help. 

I had this EXACT SAME PROBLEM on OpenSUSE Tumbleweed and now I have it on a freshly installed Manjaro Linux.


EXPECTED RESULT

Obviously should always work


SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.15.71-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.3 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: LENOVO
Product Name: 81WE
System Version: IdeaPad 3 15IIL05

ADDITIONAL INFORMATION
Comment 1 php4fan 2022-10-13 11:04:01 UTC
Btw I had reported this to OpenSUSE months ago, no reply whatsoever from them.
Comment 2 Nate Graham 2022-10-14 20:07:25 UTC
Are you using more than one screen? If so this is almost certainly Bug 456210.
Comment 3 php4fan 2022-10-14 20:29:46 UTC
No, as I said:

> I use my laptop usually with an external screen connected as the only screen (with the laptop lid closed and an external keyboard and mouse)

So, only the external monitor. Unless that count as multiple screens even though the builtin one is disabled.

Just to be clear: in Display Settings, the external monitor is the only one "enabled" and it is the "primary" one. The builtin one is not enabled.

I can't find in  Bug 456210 in what way exactly they "can't" unlock the screen, but I don't see any mention of jerky/unrsponsive behavior.
People talk about what happens after entering the password and nobody mentions being unable to enter the password in the first place.

Looks like a completely different bug to me.

BTW I'm using Xorg, not Wayland.
Comment 4 Nate Graham 2022-10-14 20:32:37 UTC
OK, thanks.
Comment 5 Nate Graham 2022-11-04 20:28:56 UTC

*** This bug has been marked as a duplicate of bug 374890 ***
Comment 6 Nate Graham 2023-10-28 17:07:10 UTC
Sorry, I think I mis-triaged this bug. It looks a lot more like Bug 437520, which I can reproduce.

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