https://bugs.kde.org/show_bug.cgi?id=517564
Bug ID: 517564
Summary: Clicking "Hibernate" on lock screen submits empty
password, triggering shake animation and aborting
hibernation
Classification: Plasma
Product: plasmashell
Version First 6.6.2
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Screen locking
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
SUMMARY
When attempting to hibernate the system from an active user's Lock Screen, the
click/Enter event on the "Hibernate" button is not fully consumed. Instead, it
bleeds through to the focused password input field. This triggers an empty
password submission, causing the "shake" animation for a failed login. This
resulting UI animation and PAM authentication attempt act as a software wake
event, which instantly aborts the kernel's hibernation sequence.
Hibernation works perfectly from the SDDM login screen (before user login) and
from the unlocked Plasma desktop. It only fails on the kscreenlocker UI.
STEPS TO REPRODUCE
Log into a Plasma session.
Lock the screen (Meta + L).
Click the "Hibernate" button on the lock screen (or highlight it with Tab and
press Enter).
OBSERVED RESULT
The password input box shakes (indicating a failed empty login attempt).
The screen goes black momentarily as hibernation begins.
The system immediately wakes back up to the lock screen.
Checking journalctl shows the image saves successfully, but is immediately
aborted by the software wake event:
PM: Image saving done
PM: hibernation: Wakeup event detected during hibernation, rolling back.
EXPECTED RESULT
The click/keypress should be consumed entirely by the Hibernate button. The
password field should not receive an enter/submit event, and the system should
successfully hibernate without being interrupted by the lock screen's UI
animation.
ADDITIONAL INFORMATION
OS: CachyOS (Arch-based)
Hardware: Intel APU Laptop
Troubleshooting performed: Completely disabled all ACPI hardware wake triggers
(/proc/acpi/wakeup) to rule out rogue USB/hardware ghosts. The issue persists,
confirming the wake event is entirely software/UI driven by the lock screen's
animation/input handling. A delayed terminal hibernation (sleep 5 && systemctl
hibernate) executed before locking the screen works perfectly, further
isolating the bug to the lock screen button's event propagation.
--
You are receiving this mail because:
You are watching all bug changes.
