Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.

I have a Lenovo IdeaPad Z570 with Ubuntu 12.04 and Windows 7. If it matters, I have a secondary NVIDIA GPU which I use Bumblebee with Primus to control (in the absence of Optimus drivers for Linux).

Every time I power down my computer from Ubuntu, it turns completely off (the shutdown process proceeds as usual and all of the lights and display turn entirely off). Then, after a few seconds, it powers back on from the very start (as if I had pressed the power button). Running 'sudo shutdown -h now' does not help. I'm asking this in Ask Ubuntu because this only occurs from my Ubuntu installation - Windows 7 does not exhibit this error.

If it matters, I recently migrated my Windows installation from a HDD to a new SSD and reinstalled Ubuntu from scratch (minus some documents in my /home directory). Any ideas?

EDIT: I believe this only happens on battery power, as I don't remember it ever happening on AC (it happens 100% right now). I don't have access to a charger at the moment, but I will try disabling laptop-mode to see if it helps.

EDIT: Setting ENABLE_LAPTOP_MODE_TOOLS=0 in /etc/laptop-mode/laptop-mode.conf seems to solve this problem, so it appears to be an issue with laptop-mode. But I'd like to maximize battery, so what can I do to fix this while keeping laptop-mode? The following errors show when I try to shutdown with laptop mode enabled - (using sudo shutdown now so I can read them without it powering off):

* Disabling laptop mode...
/lib/init/upstart-job: 28: shift: can't shift that many
/lib/init/upstart-job: 28: shift: can't shift that many
modem-manager[3415]: <info> ModemManager (version 0.5.2.0) starting...
modem-manager[3415]: 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

It repeats the bottom two three times with [3415], [3427], [3431]. After the final message it states [fail] in red on the right side and

*Will now switch to single-user mode
share|improve this question
I recommend reporting this as a bug. (This question also has some good information about bug reporting.) This may be closed as off-topic, in accordance with the FAQ and this policy. – Eliah Kagan Jan 7 at 7:19

closed as off topic by gertvdijk, Stephen Myall, hhlp, Amith KK, Luis Alvarado Jan 7 at 16:53

Questions on Ask Ubuntu are expected to relate to Ubuntu within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about closed questions here.

2 Answers

You may want to specify for the computer to power off after halting. Fire your favorite terminal and try this:

sudo shutdown -hP now

This should halt (h) your computer and power (P) it down.

share|improve this answer
Thanks, but that didn't work either. It seems to be that there's an error in the shutdown process. – Alex Jan 6 at 21:02
What is the error message that you are getting? – camconn Jan 6 at 21:13
None. 'sudo shutdown -k now' also returns nothing. Is there any file where the entire shutdown log is saved to that I could look at? Also, if you check my post, it turns out that laptop-mode is causing the issue. – Alex Jan 6 at 21:19
Wait, update. I hit ESC on the splash screen after shutting down with command line and found some errors related to laptop-mode. In my initial post now. – Alex Jan 6 at 21:28

After some extensive trial and error I managed to find the source of my problem. It was a specific module employed by laptop-mode-tools that was causing the issue. If the module in /etc/laptop-mode/conf.d labelled "runtime-pm.conf" is enabled or set to auto-enable (and the setting to automatically enable it in laptop-mode.conf is equal to 1) then this error occurs (basically, if the runtime-pm module is active on shutdown). Otherwise, it works fine.

I set this module never to enable and the rest are automatic, and it seems to be working fine. Knowing the specifics, I was able to conduct a more fruitful Google search and find people experiencing the exact same problem here.

Anyone experiencing this problem may be able to fix it by:

gksu gedit /etc/laptop-mode/conf.d/runtime-pm.conf

and changing CONTROL_RUNTIME_PM from "auto" or "1" to "0". This module will not be activated when laptop-mode is from now on, so after restarting it should be off and the shutdown error will not persist.

In addition, the errors I receive when I issue 'sudo shutdown' in the terminal seem to be unrelated to the issue.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.