I noticed this started to happen when I installed Ubuntu on separate partition. When it reaches low battery level, instead of prompting that battery is low, it just powers off (the same way you would hold a power button long enough for it to instantly shut down). The same thing is happening on Windows as-well (another partition). I can't find solution for this and it just kills me inside when it powers off like this, how can I fix this?  Laptop: Asus X552CL Year bought: 2014 OS: Ubuntu 16.04
39498
I would like my laptop to hibernate itself when the battery level is 10% to be sure it has enough power to complete the operation properly. Actually if I don't pay attention my laptop informs me it will hibernate when it's too late, so instead it brutally shuts down. This kills lithium batteries and is not acceptable.
39544
I have a Dell 7737 laptop, and with Ubuntu 16.04 it no longer suspends when the laptop lid is closed. With 14.04 closing the lid put the laptop to suspend as expected. However, I reloaded the system with Ubuntu 16.04 and now closing the laptop does nothing. The laptop continues to run as if nothing happened.  When I manually select "Suspend" from the menu it works as expected. (Though it does prompt me to double login on resume. No, not encryption login followed by OS login. This is a double OS login.)  NOTE: Altering the System Settings|Power doesn't seem to affect anything.  Any ideas on what changed from 14.04 to 16.04 in this area?
48878
Is there a way to turn off the display (enter power saving mode) using a command?  For example, when the computer is inactive for a specific interval, the screen turns off to conserve energy. Is there a way to manually turn off the screen, yet keep the computer running normally?  This is a notebook, so there's no 'power-off' button on the monitor itself.
67344
How do I change the low and critical battery levels to below 10%? I understand that this is a reasonable limit for most portable computers, but what about those with large batteries? On my computer (which has two batteries) 10% is an hour of runtime and is therefore way too high.
95209
I installed ubuntu 16.04 LTS a week after official release using the mini ISO, then ubuntu-desktop without recommended packages. Since then, just installing packages on a need to basis.   After trying to wake the computer from sleep by using the touchpad, the light on the power button stops blinking and I hear the sound of the hard drive coming online. But :    the screen stays completely off, no backlight. the laptop doesn't respond to any keyboard presses. Everytime I use The magic SysRq to restart the laptop. Long pressing the power button works too.   This problem wasn't present when using ubuntu 14.04 LTS  The proposed solutions in all the possible duplicates on this website didn't solve my problem. One big difference is that my laptop screen is off not just blank.  Possible helpful informations. All got after system reboot.       HARDWARE DETAILS :   Computer Model :   Hewlett-Packard Compaq Presario C700 Notebook PC/30D9, BIOS F.35 03/29/2010     uname -a   Linux CPC700 4.4.0-22-generic #39-Ubuntu SMP Thu May 5 16:53:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux      lspci -nn :    00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 03) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) [8086:2a03] (rev 03)      sudo lshw -class display   *-display:0    description: VGA compatible controller    product: Mobile GM965/GL960 Integrated Graphics Controller (primary)    vendor: Intel Corporation    physical id: 2    bus info: pci@0000:00:02.0    version: 03    width: 64 bits    clock: 33MHz    capabilities: msi pm vga_controller bus_master cap_list rom    configuration: driver=i915 latency=0    resources: irq:26 memory:91000000-910fffff memory:80000000-8fffffff ioport:30d0(size=8) *-display:1 UNCLAIMED    description: Display controller    product: Mobile GM965/GL960 Integrated Graphics Controller (secondary)    vendor: Intel Corporation    physical id: 2.1    bus info: pci@0000:00:02.1    version: 03    width: 64 bits    clock: 33MHz    capabilities: pm bus_master cap_list    configuration: latency=0    resources: memory:91100000-911fffff   EDIT 1 I think this is a bug, because it doesn't happen all the time anymore. I would file it as such on launchpad but I don't know which packages cause the problem. How can I go on to find them in my specific case ?  EDIT 2 With the setting "When the lid is closed : do nothing".     The system doesn't go to sleep when I close the lid. Content of listens (acpi_listen > ~/listens) :       button/lid LID close   button/lid LID open
22395
The issue is solved temporary using the method in this forum, but only if I have fresh boot, if i suspend my laptop and wake it again, Ubuntu will ignore my rules, and suspend when i close the lid.
63626
I have recently installed Xubuntu 13.10 on my Vaio vpcea making me a Linux beginner. The problem is that  laptop's power button is right on the edge of the bezel making it far too easy to press accidentally, in my opinion a design fault by Sony.  At present, when I press the power button it shuts down strait away and as you can imagine, when I'm accidentally pressing it all the time it gets very annoying! So I planned to change it to ask what I would like to do when I press it or at least ask if I'm sure.  So I went through the xfce GUI options "Settings Manager" - "Power Manager" to the field "When power button is pressed", but it was already set to "Ask". So I did some digging and found a thread telling me to navigate to /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml where it said to find power-button-action and check that  value="3". It already did.  So I looked some more and found  which focuses on acpi scripts. I tried solution 1 &amp; 2 using sudoedit to change the files accordingly (I have made executable bash shell scripts already so I think I followed them correctly), but still no difference.   I also found  which instructed me to edit /etc/systemd/logind.conf so that HandlePowerKey=ignore. Still no luck.  I even tried my own approach to completely disable /etc/acpi/powerbtn.sh by renaming it powerbtn.sh.bak hoping for at least no response from the power button... and I have done many reboots in between... but still it shuts down!  I have also read that some people have the file /etc/acpi/events/power_button, but I do not.  So does anyone have any other ideas? What else could be executing the shutdown sequence Is there something I'm missing?  I haven't undone any of these actions so every one of the above files is currently edited on my computer, with the exception that "Solution 2" automatically undone "Solution 1" above.   Thanks guys.
79641
So I have decided to make the leap from Windows to Linux, but I have been having one issue. Whenever I close the lid of my laptop, it goes into sleep mode, and when I open the lid, it comes back awake. My issue is, that 30 seconds or a minute into use, it auto goes into sleep for NO reason, I don't know why it does this. I then have to press the power button to get it to wake, but then it just repeats, I have to completely power off to fix it. Any solutions? I can provide info as needed, provided you tell me how to get that info.
80300
I have old MacBook Pro that has a dead battery.  It is not charging, and displays always 0% battery charge. OS X is downgrading performance when battery level is close to something about 5% or 10%. Is that possible to turn off this feature, to be able to use its 100% performance without exchanging battery to new?
73859
I'm a new Ubuntu 13.10 user. Closing the lid of my laptop does not result in the computer entering suspend mode, meaning each time I close my lid without manually suspending the computer the battery dies.  The proper settings are set in Power Management -- suspend the laptop on lid close for both AC and DC, but these do not have an effect on actual behavior.  It looks like this is a common problem for many users as far back as Ubuntu 11 -- the only solution I could find is the below. However, as a new linux user I'm not aware of how to actually execute the instructions. If someone could provide additional detail that would be tremendously helpful.  Thanks in advance.  /etc/acpi/events/lidbtn triggers /etc/acpi/lid.sh which triggers  /etc/acpi/local/lid.sh.post at the end of the script.  /etc/acpi/local/* allows you to add your own config (e.g. required for  wmii).   generate /etc/acpi/local/lid.sh.post  make it executable and add:   \#!/bin/bash  grep -q closed /proc/acpi/button/lid/*/state  if [ $? = 0 ]  then  /usr/sbin/pm-suspend  fi   wmii will now go to suspend mode when closing the lid. It'll  automatically wake up when opening the lid.     #!/bin/bash      load=$(cat /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/capacity)     min_load=20     if [ $load &lt;= min_load ]; then         pm-suspend     fi
54954
Cross post from   I have a laptop I'm running as a file server, which is running Ubuntu 10.04 Desktop. Now that summer heat is here, and because I love the environment, I'm look for all sorts of ways to reduce the laptop's power/memory/heat footprint.  One part I never touch any more is the GUI as the lids always closed.  I thought perhaps simply removing GDM from all run-levels my achieve this, so I did so using sysv-rc-conf. However this didn't make any difference and upon reboot the lovely Ubuntu boot screen and graphical login prompt appeared.  Please help!  Additionally, perhaps this is a silly question, I want to make sure that the monitor is off at all times the lid is closed, which it is already set to do when the GUI is running, can/do I need to configure this separately for non-GUI environments? (Seems to be doing this fine)  Thanks :D  EDIT: Ok maybe I'm using sysv-rc-conf wrong and it needed 2 reboots to apply the settings or something? As rebooting it a second time since removing GDM from all run levels I got a command prompt.  However I didn't watch it reboot and was a little confused by this, so I rebooted what I believe to be a 3rd time, and now it's booted to a black screen with a solitary white underline in the top-left, no other text. No amount of keyboard mashing in order to change run levels is having any effect, however I am able to access it via SSH and the SMB shares, so I suppose it's doing almost what I want. The lack of a CLI on the screen itself is still concerning however.
50782
My laptop boots up as normal,but using for like 10-15 minutes, screen goes black and there is red vertical line on the right side of the screen. The only thing you can do is restart it and use it again.
69204
I have looked all over the Internet trying to find a fix, but I can't seem to find one. I have a custom built PC running an AMD processor, Nvidia graphics, 16GB of ram and a 1TB HDD for Ubuntu. I am not trying to dual boot, I just have Ubuntu 13.04 on the hard drive nothing else.  Every time I press 'Shutdown' or 'Restart', it goes through its normal shutting down thing; but, after that, there is just a black screen and nothing more. Nothing happens, it's just black. The only way for me to turn off Ubuntu at the moment is to press shutdown, wait for the screen to go dark, and then force shutdown it by pressing the physical shutdown button on the PC.  Could someone please tell me what is wrong and how I can get Ubuntu to work correctly? (Never had this problem when I was dual booting on my old HDD.)  P.S. I am able to log out.  After running Sudo shutdown it gave me an error this is the error:  'Modem-manger[5062]: Could not get the system bus. Make sure the message bus daemon is running! Message: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory modem-manger[5078]:  ModeUbuntu 13.04rsion 0.6.0.0) starting... modem-manger[5078]: Could not get. . . . m bus. Make sure the message [FAIL] e   * Will now switch to single-user modenect to socket /var/run/dbus/system_bus_so root@mauritz-ubuntu:~# irectory'  And then just a ton of OK checking's, To me it seems like much of the text that it is displaying is overlapping on other text, so thats why it seems really weird.  Second error (running sudo shutdown as root): "sudo shutdown now *Disabling power management... [OK] Saned disabled; edit /etc/default/saned Speech-dispatcher disabled; edit /etc/default/speech-dispatcher  * Asking all remaining processes to terminate... [OK]  * Killing all remaining processes... [FAIL]  * Will now switch to singel-user mode"
45657
I have Macbook Air, Mac OS X El Capitan.  There is no warning box shown before the battery is near %15, like it did for Mountain Lion. So I can not notice and my computer goes sleep simply when the battery is off.  And even if it did I generally miss it because I use it external monitor attached to my Macbook Air. And because I play Spotify, I may miss the warning sound, too.  Is there warning box for low battery on El Capitan? If not, is there any utility or software that may help for external monitors and even playing music?
82892
There are many superstitions on what you must never do lest your battery become worthless - and by worthless I mean hold about 16 - 24 seconds of charge. This has happened to every laptop I have ever owned, and I just got a new one, so please help me sort out fact from fiction. Here are some of the things I've heard:   Do not keep your laptop fully charged. You must run it completely down every so often. Do not use your laptop plugged in to the wall. Only plug it in when it needs charge. If you will not be using your laptop for a long period of time, don't leave it at full charge. Do not leave your laptop running 24/7.   The first two I know to be complete fiction: this was true of old batteries such as you might have had in an iPod in 2003, but modern batteries function better when kept at or near full charge. Devices even have circuitry to prevent you from completely depleting your battery, as this is dangerous.  The third point sounds probable, and I'd be interested to know if it was true. However, it doesn't really apply to me because I'm not really the type to leave my laptop alone for a day, much less a "long period of time"  The fourth seems most likely of the above, but only because of causality: I have always done this, and my batteries have always crapped out on me. I've generally treated a laptop like a desktop with a battery backup, and that I can move from one room to another if necessary. The fact that my batteries tend to last less than 30 seconds has further entrenched this behavior. Should I be trying to break this habit?  Are there any other things that ruin laptop batteries? I love that I can actually use my new laptop unplugged :) I'd like to keep it that way.  Update: Additional question: If the computer will be used for an extended period of time plugged in, does it make sense to remove the battery first?  Update 2: I know people with laptops older than mine, who actively use their laptops as much as I do, and their batteries still hold about an hours' charge while mine holds less than 30 seconds, hence my belief that something I'm doing kills them.
116769
I want my laptop to shutdown when I close the laptop lid.  But in the power settings I can only choose between:   Suspend Do nothing Hibernate (Disabled)   Is there any way to configure it with more options?
30743
This was working perfectly on 17.10 but after upgrading to 18.04 yesterday, when the lid is closed the screen turns off but doesn't suspend properly.  I travel around a lot and immediately noticed the heat (and battery draining) when taking it out of the travel case.  I've tried uncommenting these lines in /etc/systemd/logind.conf  HandleLidSwitch=suspend HandleLidSwitchDocked=suspend   and restarted but didn't make any difference.