Bug 495729 - Unable to unlock the screen after suspending by closing the lid and waking up by opening the lid of the laptop
Summary: Unable to unlock the screen after suspending by closing the lid and waking up...
Status: RESOLVED DUPLICATE of bug 494927
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: general (show other bugs)
Version: 6.2.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-11-02 21:04 UTC by Łukasz Konieczny
Modified: 2024-11-02 21:42 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Łukasz Konieczny 2024-11-02 21:04:21 UTC
SUMMARY
When I suspend the laptop by closing it and then open it, I can't unlock the system, because neither pressing Enter after providing password nor clicking on the arrow works. Moreover, pressing Enter removes focus from the password text field and then does nothing. I have also noticed another erratic behavior. When I lock the screen and click on suspend on lock screen, the lock screen shakes as if I were providing wrong password, despite I don't want to provide password, but to suspend the system. Maybe this observation will help in debugging.

STEPS TO REPRODUCE
1. Close the laptop.
2. Open the laptop.
3. Provide password.
4. Observe, that you can't unlock the system.

OBSERVED RESULT
Inability to unlock the system

EXPECTED RESULT
Ability to unlock the system

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.2.2
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.6-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® Xe Graphics
Manufacturer: System76
Product Name: Darter Pro
System Version: darp7

ADDITIONAL INFORMATION
Comment 1 Antonio Rojas 2024-11-02 21:42:46 UTC

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