Hibernate doesn't support as the default action in Ubuntu when critical power
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Confirmed
|
High
|
jeremyszu | ||
gnome-settings-daemon (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
upower (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
In a stock ubuntu 20.04.3, g-s-d will notify the critical action when battery is lower than warned critical threshold.
The notification is "The battery is below the critical level and this computer is about to hibernate."
When hitting critical threshold, it takes "HybirdSleep" as the action.
```
九 29 11:24:48 ubuntu-
九 29 11:24:48 ubuntu-
九 29 11:24:48 ubuntu-
九 29 11:24:48 ubuntu-
九 29 11:24:48 ubuntu-
```
You could see the hibernation called by logind but it will fail to restore since either not enough SWAP or resume address is not specify to kernel.
It confusing users about the critical actions.
In UPower.conf:
```
$ tail etc/UPower.conf
# reached for the batteries (UPS or laptop batteries) supplying the computer
#
# Possible values are:
# PowerOff
# Hibernate
# HybridSleep
#
# If HybridSleep isn't available, Hibernate will be used
# If Hibernate isn't available, PowerOff will be used
CriticalPowerAc
```
In g-s-d:
```
/* We don't make the difference between HybridSleep and Hibernate */
if (g_strcmp0 (action, "PowerOff") == 0)
else
...
```
There are two approach if possible:
1) change "CriticalPowerA
2) have a new "GsdPowerAction
---
$ dpkg -l | grep -i 'upower\
ii gir1.2-
ii gnome-settings-
ii gnome-settings-
ii libupower-
ii upower 0.99.11-1build2 amd64 abstraction for power managemen
tags: | added: oem-priority originate-from-1943959 stella |
tags: | added: originate-from-1911231 |
summary: |
- Hibernate is not the default action in Ubuntu when critical power + Hibernate doesn't support as the default action in Ubuntu when critical + power |
Changed in oem-priority: | |
assignee: | nobody → jeremyszu (os369510) |
importance: | Undecided → High |
status: | New → Confirmed |
Thanks Jeremy, could you open it for discussion upstream. There had been similar problems discussed in the past, see https:/ /gitlab. gnome.org/ GNOME/gnome- settings- daemon/ -/issues/ 547 , is the outcome matching what you can observe?