Bug 353356 - Powerdevil does not respect the critical level configuration
Summary: Powerdevil does not respect the critical level configuration
Status: RESOLVED WORKSFORME
Alias: None
Product: Powerdevil
Classification: Plasma
Component: general (show other bugs)
Version: 5.4.1
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Development Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-30 07:30 UTC by Salvo "LtWorf" Tomaselli
Modified: 2020-12-12 04:34 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Salvo "LtWorf" Tomaselli 2015-09-30 07:30:42 UTC
From the battery monitor thing I've configured that the action to take when the battery reaches a critical level is to suspend the machine.

However, yesterday the action that was taken was to shut it down completely, which is also not a very good thing to do, because systemd has very long timeouts before terminating processes, so it might be the case that the shutdown takes longer than the battery. Suspending to RAM is faster.

Reproducible: Always

Steps to Reproduce:
Set suspend as action
Let the battery drain
Comment 1 Kai Uwe Broulik 2015-11-23 15:33:45 UTC
Can you check what is configured in System Settings → Power Management → At critical battery
Comment 2 Salvo "LtWorf" Tomaselli 2015-11-23 16:48:47 UTC
Critical is 6%, low is 10%
Comment 3 Salvo "LtWorf" Tomaselli 2015-12-26 22:46:41 UTC
asd
Comment 4 Justin Zobel 2020-11-12 22:37:23 UTC
I've just tested this and my laptop automatically suspended at the critical level (60s timeout).

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 5 Bug Janitor Service 2020-11-27 04:33:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2020-12-12 04:34:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!