Bug 490557

Summary:	Laptop can leave sleeping mode while lid is closed
Product:	[Plasma] plasmashell	Reporter:	Elias Fierke <elias.fierke>
Component:	Power management & brightness	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	chris, elias.fierke, jpetso, natalie_clarius, nate, postix
Priority:	NOR
Version First Reported In:	6.2.4
Target Milestone:	1.0
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed In:	6.3.0
Sentry Crash Report:

Description Elias Fierke 2024-07-20 13:01:31 UTC

SUMMARY
Seems to be that the keyboard is still activated when lid is closed and the device goes into sleeping-mode. When pressing a key when the lid is closed (I think the display itself presses some keys) the computer wakes up and the display turns on.

STEPS TO REPRODUCE
1. Close your laptops lid with "What happens when lid is closed"-Setting set to "sleep"
2. Slightly open the lid so that the display does NOT turn on (laptop doesn't wake up from sleep) an press a key with a rubber or so.
3. Display should turn on even though lid is closed. 

PROBLEM
This drains the battery and causes the system to maybe overload when many buttons are pressed by the display.


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40, Plasma 6.1


SOLUTION
Second event-handling case for lid-closed-sleep: Keyboard should be deactivated and only be reactivated after opening the lid.

Comment 1 Jakob Petsovits 2024-07-24 10:36:46 UTC

This is generally pretty difficult because we don't get to hear about the cause of the system being woken up. Not sure if the kernel even knows about it. There have been past efforts to make the system suspend again when the lid is still closed (https://invent.kde.org/plasma/powerdevil/-/merge_requests/279) and there is some potential for Plasma to make improvements this way, but it's not easy to get right without introducing regressions.

Comment 2 Nate Graham 2025-05-07 20:28:38 UTC

Should be fixed with https://invent.kde.org/plasma/powerdevil/-/merge_requests/489 in Plasma 6.3

Comment 3 Nate Graham 2025-05-07 20:52:04 UTC

*** Bug 497768 has been marked as a duplicate of this bug. ***