← Back to team overview

documentation-packages team mailing list archive

[Bug 1599264] Re: "When power is critically low" setting does nothing

 

Thanks for the docs hint, Will. Suppose it affects this page:

https://help.ubuntu.com/stable/ubuntu-help/power-lowpower.html

** Changed in: ubuntu-docs (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-docs (Ubuntu)
       Status: New => Confirmed

** Changed in: ubuntu-docs (Ubuntu Xenial)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1599264

Title:
  "When power is critically low" setting does nothing

Status in ubuntu-docs package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in ubuntu-docs source package in Xenial:
  Won't Fix
Status in unity-control-center source package in Xenial:
  New
Status in ubuntu-docs source package in Yakkety:
  Confirmed
Status in unity-control-center source package in Yakkety:
  Confirmed

Bug description:
  Since the move to systemd (I think) the setting in unity-control-
  center under "Power" that says:

  When power is critically low: [Hibernate | Power Off]

  doesn't actually do anything any more.

  That action is now controlled by Upower config in
  /etc/UPower/UPower.conf.  At the end of that file you can see:

  # The action to take when "TimeAction" or "PercentageAction" above has been
  # 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
  CriticalPowerAction=HybridSleep

  
  So the default action is HybridSleep and is not configurable by the user in the control center anymore.

  FWIW - I think the best thing to do is just remove that setting from
  u-c-c altogether.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1599264/+subscriptions