Bug 505027

Summary:	Critical Battery State not Properly Exited during Sleep
Product:	[Plasma] plasmashell	Reporter:	Skylyn Bilen <skylyn.bilen.sb>
Component:	Power management & brightness	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	minor	CC:	nate
Priority:	NOR
Version First Reported In:	6.3.5
Target Milestone:	1.0
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Skylyn Bilen 2025-05-30 18:02:48 UTC

SUMMARY


STEPS TO REPRODUCE
1. Drain battery to critical
2. Sleep/suspend
3. Charge during sleep/suspend
4. Unplug, computer still asleep/suspended
5. Wake, log in.*
6. Set screen brightness.
7. Drain battery to critical again.**

OBSERVED RESULT
*: the battery critical notification is not cleared
**: The screen brightness isn't changed as the Battery Critical notification is shown again.

EXPECTED RESULT
*: The battery critical notification is cleared/revoked
**: The screen brightness is set to what's set in the battery critical power setting.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
KDE Plasma Version: 6.x (Currently 6.3.5)
KDE Frameworks Version:  6.x (currently 6.14.0)
Qt Version: 6.x (currently 6.9.0)

ADDITIONAL INFORMATION
Due to the time consuming nature of testing this, I'm unable to provide more information on how this behavior... behaves, in a timely manner.
This may or may not be important: The "On battery" power state has the option that sets the screen brightness disabled.

Comment 1 Nate Graham 2025-05-30 19:43:51 UTC

Pretty sure I've seen this myself. Sounds a bit like Bug 471636. It would appear we need to re-evaluate the battery percentage when waking from sleep.

Comment 2 Skylyn Bilen 2025-06-01 14:50:45 UTC

Additional information and accidental discovery: turns out, if you sleep during the hibernate timer, it will force hibernate even with a mostly full battery. This went from a minor inconvenience to a rather loud bug.

Comment 3 Nate Graham 2025-08-06 23:26:08 UTC


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