Just to give a little spin to this issue: I disabled the CriticalPowerAction on my system via
apt-get source upower
apt-get build-dep upower
This patch:
--- upower-v0.99.17/src/up-daemon.c.orig 2023-07-24 08:49:57.687894559
+0200
+++ upower-v0.99.17/src/up-daemon.c 2023-07-24 08:49:59.911791573 +0200
@@ -674,6 +674,8 @@
!daemon->priv->use_percentage_for_policy &&
time_to_empty > 0.0)
use_percentage = FALSE;
+// ThOr Hack: disable the stuff. No powering off when I do not want it.
+return default_level;
if (use_percentage) {
if (percentage > daemon->priv->low_percentage)
--- upower-v0.99.17/debian/changelog.orig 2023-07-24 08:54:00.024666085
+0200
+++ upower-v0.99.17/debian/changelog 2023-07-24 08:54:10.496180631 +0200
@@ -1,3 +1,9 @@
+upower (0.99.17-99thor) unstable; urgency=medium
+
+ * hack it for not doing any critical action
+
+ -- Thomas Orgis <tho...@orgis.org> Fri, 21 Jul 2023 22:49:00 +0200
+
upower (0.99.17-1) unstable; urgency=medium
* New upstream version 0.99.17
Then:
apt-get --build source upower
dpkg -i upower_0.99.17-99thor_amd64.deb
(matching libupower package, too, but that isn't necessary, I think)
Of course, a proper setting upstream would be preferrable, but I needed
a solution now for battery gauge training where the voltage is below 2%
for a considerable time.
Alrighty then,
Thomas
pgprghGDg3V_A.pgp
Description: Firma digital OpenPGP
