documentation-packages team mailing list archive
Mailing list archive
[Bug 1599264] Re: [SRU] "When power is critically low" setting does nothing
** Changed in: ubuntu-docs (Ubuntu Z-series)
Assignee: (unassigned) => Chris Perry (clissold345)
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
[SRU] "When power is critically low" setting does nothing
Status in One Hundred Papercuts:
Status in ubuntu-docs package in Ubuntu:
Status in unity-control-center package in Ubuntu:
Status in ubuntu-docs source package in Xenial:
Status in unity-control-center source package in Xenial:
Status in ubuntu-docs source package in Yakkety:
Status in unity-control-center source package in Yakkety:
Status in ubuntu-docs source package in z-series:
In unity-control-center (u-c-c) there is an option for taking an
action when "Power is critically low". The choices are "Hibernate" or
"Power off". Often Hibernate is a disabled option because of problems
with hibernate on various systems.
However - what to do in the event of a critically low power situation
is now handled by Upowerd automatically and so making a choice in
u-c-c does nothing at all.
As such, leaving that option accessible to users will lead to
This patch removes the option from the UI.
On an unpatched machine with a battery (i.e. laptop) open the power
panel in u-c-c (Power/Settings menu in the top right corner -> System
Settings -> Power. Note that the 2nd option down is "When power is
Once this update is applied and u-c-c is closed and reopened, this
option is no longer present.
There are some deletions from the ui file and some corresponding code deletions from the associated c file (cc-power-panel.c).
It is possible that extra code has been removed that could cause a
crash or affect other options in the power panel.
However, the changes are fairly small and easy to review. Nothing
looks out of place. Also testing has not shown any problems.
Verbal (IRC) +1 from design via mpt.
+1 from docs team via mailing list.
To manage notifications about this bug go to: