Laptop not shutting down on low powerDifference between dconf power settings and Upower.conf?Laptop immediately suspends when going onto battery powerLow-battery-power action without gnome-power-managerSuspend when critically low power 11.10Asus laptop power managementLaptop slow performance on battery power

Are there any real life instances of aircraft aborting a landing to avoid a vehicle?

Do animals summoned by the Conjure Animals spell get extra HP from Circle of the Shepherd's Spirit Totem ability?

What does a single quote inside a C# date time format mean?

numpy 1D array: mask elements that repeat more than n times

Replacing triangulated categories with something better

Why is the Falcon Heavy center core recovery done at sea?

Using parent's property and will as evidence of assets

Run "cd" command as superuser in Linux

How would a young girl/boy (about 14) who never gets old survive in the 16th century?

Do effects that prevent someone from becoming an undead stop or delay the effect?

How is warfare affected when armor has (temporarily) outpaced guns? How can guns compete?

Why is the past tense of vomit generally spelled 'vomited' rather than 'vomitted'?

Is exploit-free software possible?

Is velocity a valid measure of team and process improvement?

What are some examples of three-mora atamadaka verbs besides 帰る?

How does a manufacturer determine the warranty for the battery?

What is the "more" means here?

Why is my Windows 7 recovery folder 53% of my disk

Uncountably many functions coinciding only finitely many values

How to help my son improve without being discouraging?

Chromatic abberation in lens

What are the applications of the Mean Value Theorem?

How can I determine if two vertices on a polygon are consecutive?

Who axiomatized classical mechanics in 1949?



Laptop not shutting down on low power


Difference between dconf power settings and Upower.conf?Laptop immediately suspends when going onto battery powerLow-battery-power action without gnome-power-managerSuspend when critically low power 11.10Asus laptop power managementLaptop slow performance on battery power






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;









1

















I have problem with Ubuntu 19.04. System doesn't shutdown in normal way when battery is low. When battery level drops to 3% laptop is turning off like I pulled out the battery.










share|improve this question


























  • Are you using tlp?

    – WinEunuuchs2Unix
    Jun 8 at 18:35











  • How to check of system is using tlp?

    – QkiZ
    Jun 10 at 5:35












  • Use systemctl status tlp

    – WinEunuuchs2Unix
    Jun 10 at 10:27











  • Unit tlp.service could not be found.

    – QkiZ
    Jun 10 at 18:30

















1

















I have problem with Ubuntu 19.04. System doesn't shutdown in normal way when battery is low. When battery level drops to 3% laptop is turning off like I pulled out the battery.










share|improve this question


























  • Are you using tlp?

    – WinEunuuchs2Unix
    Jun 8 at 18:35











  • How to check of system is using tlp?

    – QkiZ
    Jun 10 at 5:35












  • Use systemctl status tlp

    – WinEunuuchs2Unix
    Jun 10 at 10:27











  • Unit tlp.service could not be found.

    – QkiZ
    Jun 10 at 18:30













1












1








1








I have problem with Ubuntu 19.04. System doesn't shutdown in normal way when battery is low. When battery level drops to 3% laptop is turning off like I pulled out the battery.










share|improve this question















I have problem with Ubuntu 19.04. System doesn't shutdown in normal way when battery is low. When battery level drops to 3% laptop is turning off like I pulled out the battery.







laptop battery






share|improve this question














share|improve this question











share|improve this question




share|improve this question










asked Jun 8 at 18:30









QkiZQkiZ

7751 gold badge6 silver badges27 bronze badges




7751 gold badge6 silver badges27 bronze badges















  • Are you using tlp?

    – WinEunuuchs2Unix
    Jun 8 at 18:35











  • How to check of system is using tlp?

    – QkiZ
    Jun 10 at 5:35












  • Use systemctl status tlp

    – WinEunuuchs2Unix
    Jun 10 at 10:27











  • Unit tlp.service could not be found.

    – QkiZ
    Jun 10 at 18:30

















  • Are you using tlp?

    – WinEunuuchs2Unix
    Jun 8 at 18:35











  • How to check of system is using tlp?

    – QkiZ
    Jun 10 at 5:35












  • Use systemctl status tlp

    – WinEunuuchs2Unix
    Jun 10 at 10:27











  • Unit tlp.service could not be found.

    – QkiZ
    Jun 10 at 18:30
















Are you using tlp?

– WinEunuuchs2Unix
Jun 8 at 18:35





Are you using tlp?

– WinEunuuchs2Unix
Jun 8 at 18:35













How to check of system is using tlp?

– QkiZ
Jun 10 at 5:35






How to check of system is using tlp?

– QkiZ
Jun 10 at 5:35














Use systemctl status tlp

– WinEunuuchs2Unix
Jun 10 at 10:27





Use systemctl status tlp

– WinEunuuchs2Unix
Jun 10 at 10:27













Unit tlp.service could not be found.

– QkiZ
Jun 10 at 18:30





Unit tlp.service could not be found.

– QkiZ
Jun 10 at 18:30










1 Answer
1






active

oldest

votes


















1


















Unless something has changed recently you should have this file: /etc/UPower/UPower.conf containing:



# Only the system vendor should modify this file, ordinary users
# should not have to change anything.

[UPower]

# Enable the Watts Up Pro device.
#
# The Watts Up Pro contains a generic FTDI USB device without a specific
# vendor and product ID. When we probe for WUP devices, we can cause
# the user to get a perplexing "Device or resource busy" error when
# attempting to use their non-WUP device.
#
# The generic FTDI device is known to also be used on:
#
# - Sparkfun FT232 breakout board
# - Parallax Propeller
#
# default=false
EnableWattsUpPro=false

# Don't poll the kernel for battery level changes.
#
# Some hardware will send us battery level changes through
# events, rather than us having to poll for it. This option
# allows disabling polling for hardware that sends out events.
#
# default=false
NoPollBatteries=false

# Do we ignore the lid state
#
# Some laptops are broken. The lid state is either inverted, or stuck
# on or off. We can't do much to fix these problems, but this is a way
# for users to make the laptop panel vanish, a state that might be used
# by a couple of user-space daemons. On Linux systems, see also
# logind.conf(5).
#
# default=false
IgnoreLid=false

# Policy for warnings and action based on battery levels
#
# Whether battery percentage based policy should be used. The default
# is to use the time left, change to true to use the percentage, which
# should work around broken firmwares. It is also more reliable than
# the time left (frantically saving all your files is going to use more
# battery than letting it rest for example).
# default=true
UsePercentageForPolicy=true

# When UsePercentageForPolicy is true, the levels at which UPower will
# consider the battery low, critical, or take action for the critical
# battery level.
#
# This will also be used for batteries which don't have time information
# such as that of peripherals.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# PercentageLow=10
# PercentageCritical=3
# PercentageAction=2
PercentageLow=10
PercentageCritical=3
PercentageAction=2

# When UsePercentageForPolicy is false, the time remaining at which UPower
# will consider the battery low, critical, or take action for the critical
# battery level.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# TimeLow=1200
# TimeCritical=300
# TimeAction=120
TimeLow=1200
TimeCritical=300
TimeAction=120

# 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


When percentage is true (default), the lines:



PercentageLow=10
PercentageCritical=3
PercentageAction=2


Means at 10% remaining you are told battery is running low. At 3% remaining a critical warning is issued saying battery is about to die. At 2% remaining your machine shuts down.



When percentage is false, the lines:



TimeLow=1200
TimeCritical=300
TimeAction=120


Means at 1200 seconds (20 minutes) remaining you are told battery is running low. At 300 seconds (5 minutes) remaining a critical warning is issued saying battery is about to die. At 120 seconds (2 minutes) remaining your machine shuts down.



The configuration file settings should be duplicated in gsettings which you can confirm with:



$ gsettings list-recursively | grep plugins.power | grep time
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power use-time-for-policy true


and with:



$ gsettings list-recursively | grep plugins.power | grep percentage
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-action 2





share|improve this answer




























  • thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

    – QkiZ
    Jun 11 at 20:38











  • The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

    – WinEunuuchs2Unix
    Jun 12 at 10:34












Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);














draft saved

draft discarded
















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1149643%2flaptop-not-shutting-down-on-low-power%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown


























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1


















Unless something has changed recently you should have this file: /etc/UPower/UPower.conf containing:



# Only the system vendor should modify this file, ordinary users
# should not have to change anything.

[UPower]

# Enable the Watts Up Pro device.
#
# The Watts Up Pro contains a generic FTDI USB device without a specific
# vendor and product ID. When we probe for WUP devices, we can cause
# the user to get a perplexing "Device or resource busy" error when
# attempting to use their non-WUP device.
#
# The generic FTDI device is known to also be used on:
#
# - Sparkfun FT232 breakout board
# - Parallax Propeller
#
# default=false
EnableWattsUpPro=false

# Don't poll the kernel for battery level changes.
#
# Some hardware will send us battery level changes through
# events, rather than us having to poll for it. This option
# allows disabling polling for hardware that sends out events.
#
# default=false
NoPollBatteries=false

# Do we ignore the lid state
#
# Some laptops are broken. The lid state is either inverted, or stuck
# on or off. We can't do much to fix these problems, but this is a way
# for users to make the laptop panel vanish, a state that might be used
# by a couple of user-space daemons. On Linux systems, see also
# logind.conf(5).
#
# default=false
IgnoreLid=false

# Policy for warnings and action based on battery levels
#
# Whether battery percentage based policy should be used. The default
# is to use the time left, change to true to use the percentage, which
# should work around broken firmwares. It is also more reliable than
# the time left (frantically saving all your files is going to use more
# battery than letting it rest for example).
# default=true
UsePercentageForPolicy=true

# When UsePercentageForPolicy is true, the levels at which UPower will
# consider the battery low, critical, or take action for the critical
# battery level.
#
# This will also be used for batteries which don't have time information
# such as that of peripherals.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# PercentageLow=10
# PercentageCritical=3
# PercentageAction=2
PercentageLow=10
PercentageCritical=3
PercentageAction=2

# When UsePercentageForPolicy is false, the time remaining at which UPower
# will consider the battery low, critical, or take action for the critical
# battery level.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# TimeLow=1200
# TimeCritical=300
# TimeAction=120
TimeLow=1200
TimeCritical=300
TimeAction=120

# 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


When percentage is true (default), the lines:



PercentageLow=10
PercentageCritical=3
PercentageAction=2


Means at 10% remaining you are told battery is running low. At 3% remaining a critical warning is issued saying battery is about to die. At 2% remaining your machine shuts down.



When percentage is false, the lines:



TimeLow=1200
TimeCritical=300
TimeAction=120


Means at 1200 seconds (20 minutes) remaining you are told battery is running low. At 300 seconds (5 minutes) remaining a critical warning is issued saying battery is about to die. At 120 seconds (2 minutes) remaining your machine shuts down.



The configuration file settings should be duplicated in gsettings which you can confirm with:



$ gsettings list-recursively | grep plugins.power | grep time
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power use-time-for-policy true


and with:



$ gsettings list-recursively | grep plugins.power | grep percentage
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-action 2





share|improve this answer




























  • thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

    – QkiZ
    Jun 11 at 20:38











  • The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

    – WinEunuuchs2Unix
    Jun 12 at 10:34















1


















Unless something has changed recently you should have this file: /etc/UPower/UPower.conf containing:



# Only the system vendor should modify this file, ordinary users
# should not have to change anything.

[UPower]

# Enable the Watts Up Pro device.
#
# The Watts Up Pro contains a generic FTDI USB device without a specific
# vendor and product ID. When we probe for WUP devices, we can cause
# the user to get a perplexing "Device or resource busy" error when
# attempting to use their non-WUP device.
#
# The generic FTDI device is known to also be used on:
#
# - Sparkfun FT232 breakout board
# - Parallax Propeller
#
# default=false
EnableWattsUpPro=false

# Don't poll the kernel for battery level changes.
#
# Some hardware will send us battery level changes through
# events, rather than us having to poll for it. This option
# allows disabling polling for hardware that sends out events.
#
# default=false
NoPollBatteries=false

# Do we ignore the lid state
#
# Some laptops are broken. The lid state is either inverted, or stuck
# on or off. We can't do much to fix these problems, but this is a way
# for users to make the laptop panel vanish, a state that might be used
# by a couple of user-space daemons. On Linux systems, see also
# logind.conf(5).
#
# default=false
IgnoreLid=false

# Policy for warnings and action based on battery levels
#
# Whether battery percentage based policy should be used. The default
# is to use the time left, change to true to use the percentage, which
# should work around broken firmwares. It is also more reliable than
# the time left (frantically saving all your files is going to use more
# battery than letting it rest for example).
# default=true
UsePercentageForPolicy=true

# When UsePercentageForPolicy is true, the levels at which UPower will
# consider the battery low, critical, or take action for the critical
# battery level.
#
# This will also be used for batteries which don't have time information
# such as that of peripherals.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# PercentageLow=10
# PercentageCritical=3
# PercentageAction=2
PercentageLow=10
PercentageCritical=3
PercentageAction=2

# When UsePercentageForPolicy is false, the time remaining at which UPower
# will consider the battery low, critical, or take action for the critical
# battery level.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# TimeLow=1200
# TimeCritical=300
# TimeAction=120
TimeLow=1200
TimeCritical=300
TimeAction=120

# 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


When percentage is true (default), the lines:



PercentageLow=10
PercentageCritical=3
PercentageAction=2


Means at 10% remaining you are told battery is running low. At 3% remaining a critical warning is issued saying battery is about to die. At 2% remaining your machine shuts down.



When percentage is false, the lines:



TimeLow=1200
TimeCritical=300
TimeAction=120


Means at 1200 seconds (20 minutes) remaining you are told battery is running low. At 300 seconds (5 minutes) remaining a critical warning is issued saying battery is about to die. At 120 seconds (2 minutes) remaining your machine shuts down.



The configuration file settings should be duplicated in gsettings which you can confirm with:



$ gsettings list-recursively | grep plugins.power | grep time
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power use-time-for-policy true


and with:



$ gsettings list-recursively | grep plugins.power | grep percentage
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-action 2





share|improve this answer




























  • thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

    – QkiZ
    Jun 11 at 20:38











  • The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

    – WinEunuuchs2Unix
    Jun 12 at 10:34













1














1










1









Unless something has changed recently you should have this file: /etc/UPower/UPower.conf containing:



# Only the system vendor should modify this file, ordinary users
# should not have to change anything.

[UPower]

# Enable the Watts Up Pro device.
#
# The Watts Up Pro contains a generic FTDI USB device without a specific
# vendor and product ID. When we probe for WUP devices, we can cause
# the user to get a perplexing "Device or resource busy" error when
# attempting to use their non-WUP device.
#
# The generic FTDI device is known to also be used on:
#
# - Sparkfun FT232 breakout board
# - Parallax Propeller
#
# default=false
EnableWattsUpPro=false

# Don't poll the kernel for battery level changes.
#
# Some hardware will send us battery level changes through
# events, rather than us having to poll for it. This option
# allows disabling polling for hardware that sends out events.
#
# default=false
NoPollBatteries=false

# Do we ignore the lid state
#
# Some laptops are broken. The lid state is either inverted, or stuck
# on or off. We can't do much to fix these problems, but this is a way
# for users to make the laptop panel vanish, a state that might be used
# by a couple of user-space daemons. On Linux systems, see also
# logind.conf(5).
#
# default=false
IgnoreLid=false

# Policy for warnings and action based on battery levels
#
# Whether battery percentage based policy should be used. The default
# is to use the time left, change to true to use the percentage, which
# should work around broken firmwares. It is also more reliable than
# the time left (frantically saving all your files is going to use more
# battery than letting it rest for example).
# default=true
UsePercentageForPolicy=true

# When UsePercentageForPolicy is true, the levels at which UPower will
# consider the battery low, critical, or take action for the critical
# battery level.
#
# This will also be used for batteries which don't have time information
# such as that of peripherals.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# PercentageLow=10
# PercentageCritical=3
# PercentageAction=2
PercentageLow=10
PercentageCritical=3
PercentageAction=2

# When UsePercentageForPolicy is false, the time remaining at which UPower
# will consider the battery low, critical, or take action for the critical
# battery level.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# TimeLow=1200
# TimeCritical=300
# TimeAction=120
TimeLow=1200
TimeCritical=300
TimeAction=120

# 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


When percentage is true (default), the lines:



PercentageLow=10
PercentageCritical=3
PercentageAction=2


Means at 10% remaining you are told battery is running low. At 3% remaining a critical warning is issued saying battery is about to die. At 2% remaining your machine shuts down.



When percentage is false, the lines:



TimeLow=1200
TimeCritical=300
TimeAction=120


Means at 1200 seconds (20 minutes) remaining you are told battery is running low. At 300 seconds (5 minutes) remaining a critical warning is issued saying battery is about to die. At 120 seconds (2 minutes) remaining your machine shuts down.



The configuration file settings should be duplicated in gsettings which you can confirm with:



$ gsettings list-recursively | grep plugins.power | grep time
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power use-time-for-policy true


and with:



$ gsettings list-recursively | grep plugins.power | grep percentage
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-action 2





share|improve this answer
















Unless something has changed recently you should have this file: /etc/UPower/UPower.conf containing:



# Only the system vendor should modify this file, ordinary users
# should not have to change anything.

[UPower]

# Enable the Watts Up Pro device.
#
# The Watts Up Pro contains a generic FTDI USB device without a specific
# vendor and product ID. When we probe for WUP devices, we can cause
# the user to get a perplexing "Device or resource busy" error when
# attempting to use their non-WUP device.
#
# The generic FTDI device is known to also be used on:
#
# - Sparkfun FT232 breakout board
# - Parallax Propeller
#
# default=false
EnableWattsUpPro=false

# Don't poll the kernel for battery level changes.
#
# Some hardware will send us battery level changes through
# events, rather than us having to poll for it. This option
# allows disabling polling for hardware that sends out events.
#
# default=false
NoPollBatteries=false

# Do we ignore the lid state
#
# Some laptops are broken. The lid state is either inverted, or stuck
# on or off. We can't do much to fix these problems, but this is a way
# for users to make the laptop panel vanish, a state that might be used
# by a couple of user-space daemons. On Linux systems, see also
# logind.conf(5).
#
# default=false
IgnoreLid=false

# Policy for warnings and action based on battery levels
#
# Whether battery percentage based policy should be used. The default
# is to use the time left, change to true to use the percentage, which
# should work around broken firmwares. It is also more reliable than
# the time left (frantically saving all your files is going to use more
# battery than letting it rest for example).
# default=true
UsePercentageForPolicy=true

# When UsePercentageForPolicy is true, the levels at which UPower will
# consider the battery low, critical, or take action for the critical
# battery level.
#
# This will also be used for batteries which don't have time information
# such as that of peripherals.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# PercentageLow=10
# PercentageCritical=3
# PercentageAction=2
PercentageLow=10
PercentageCritical=3
PercentageAction=2

# When UsePercentageForPolicy is false, the time remaining at which UPower
# will consider the battery low, critical, or take action for the critical
# battery level.
#
# If any value is invalid, or not in descending order, the defaults
# will be used.
#
# Defaults:
# TimeLow=1200
# TimeCritical=300
# TimeAction=120
TimeLow=1200
TimeCritical=300
TimeAction=120

# 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


When percentage is true (default), the lines:



PercentageLow=10
PercentageCritical=3
PercentageAction=2


Means at 10% remaining you are told battery is running low. At 3% remaining a critical warning is issued saying battery is about to die. At 2% remaining your machine shuts down.



When percentage is false, the lines:



TimeLow=1200
TimeCritical=300
TimeAction=120


Means at 1200 seconds (20 minutes) remaining you are told battery is running low. At 300 seconds (5 minutes) remaining a critical warning is issued saying battery is about to die. At 120 seconds (2 minutes) remaining your machine shuts down.



The configuration file settings should be duplicated in gsettings which you can confirm with:



$ gsettings list-recursively | grep plugins.power | grep time
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power use-time-for-policy true


and with:



$ gsettings list-recursively | grep plugins.power | grep percentage
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-action 2






share|improve this answer















share|improve this answer




share|improve this answer








edited Jun 10 at 22:56

























answered Jun 10 at 22:45









WinEunuuchs2UnixWinEunuuchs2Unix

59.7k18 gold badges119 silver badges234 bronze badges




59.7k18 gold badges119 silver badges234 bronze badges















  • thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

    – QkiZ
    Jun 11 at 20:38











  • The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

    – WinEunuuchs2Unix
    Jun 12 at 10:34

















  • thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

    – QkiZ
    Jun 11 at 20:38











  • The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

    – WinEunuuchs2Unix
    Jun 12 at 10:34
















thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

– QkiZ
Jun 11 at 20:38





thx, thats more clear for me. but why upower settings and gnome settings daemon should be duplicated?

– QkiZ
Jun 11 at 20:38













The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

– WinEunuuchs2Unix
Jun 12 at 10:34





The Upower settings are stored permanently on disk. During boot the gnome settings are derived from that. Operationally applications access gnome settings for speed and ease of access. On power off gnome settings are lost.

– WinEunuuchs2Unix
Jun 12 at 10:34


















draft saved

draft discarded















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1149643%2flaptop-not-shutting-down-on-low-power%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown









Popular posts from this blog

Tamil (spriik) Luke uk diar | Nawigatjuun

Align equal signs while including text over equalitiesAMS align: left aligned text/math plus multicolumn alignmentMultiple alignmentsAligning equations in multiple placesNumbering and aligning an equation with multiple columnsHow to align one equation with another multline equationUsing \ in environments inside the begintabularxNumber equations and preserving alignment of equal signsHow can I align equations to the left and to the right?Double equation alignment problem within align enviromentAligned within align: Why are they right-aligned?

Training a classifier when some of the features are unknownWhy does Gradient Boosting regression predict negative values when there are no negative y-values in my training set?How to improve an existing (trained) classifier?What is effect when I set up some self defined predisctor variables?Why Matlab neural network classification returns decimal values on prediction dataset?Fitting and transforming text data in training, testing, and validation setsHow to quantify the performance of the classifier (multi-class SVM) using the test data?How do I control for some patients providing multiple samples in my training data?Training and Test setTraining a convolutional neural network for image denoising in MatlabShouldn't an autoencoder with #(neurons in hidden layer) = #(neurons in input layer) be “perfect”?