[Dell Inspiron 1720] System does not power off reliably when "Shut Down" chosen from GUI

[Mark Schneider]

Shutting down the computer using the menue does not work always correct. It often does not complete turn off the computer. The power LED and the LED of the bluetooth unit remain on. Also the fan is still running and won't stop.
Shutting down the computer with "sudo shutdown -h now" using the terminal works fine.

I am using a Dell Inspiron 1720.

[Bilal Akhtar (bilalakhtar)]

Does this always happen? This might be hardware related, I guess.

[Mark Schneider (mc-monti)]

As far as I remember it never did a complete shutdown. I always need to push the power button a long time to really turn off the notebook.

[Mark Schneider (mc-monti)]

I made a complete reinstall of the system just to make sure that nothing messed up during the update process from 10.04 LTS to 12.04 LTS. But the behaviour is still the same, no complete shutdown in 12.04.

[Mark Schneider (mc-monti)]

Some additional informations:
If I shutdown my notebook right after booting it does make a complete shutdown. It seems like the longer I wait and work with it the higher are chances for a failure. I really tried to make it reproducible without success for now.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[j-stuffer (j-stuffer)]

Same here. I don't always encounter the problem, but I think the longer the Laptop runs, the chances are bigger that it won't shut down.
Dell Studio 1558. Ubuntu 12.04 64 Bit. Fresh install. As far as I can remember I didn't have the problem in 10.04 and it started after I made an upgrade to 10.11 or 11.04 - but I'm not 100% sure. I thought a fresh install could solve it, but no success.

[Mark Schneider (mc-monti)]

I found out that a shutdown using the terminal is not always working correct. I started using it constantly today and already the second time I used it happened the failure.

[Michael Kogan (michael-kogan)]

Same problem with Xubuntu Precise. Using fglrx. The problem is not reproducible though, it appears sporadically.

[James Hunt (jamesodhunt)]

This problem sounds like it could be kernel issue.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 987220

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mark Schneider (mc-monti)]

apport information

[Richard Schmidt (ribiku-sith)]

Same Problem on a Lenovo T61P. System also freese by closing the cover. Ubuntu 12.04 with nvidia card.

[Manuel (manuel-kuederli)]

Same with hp notebook 2510p. No shutdown possible. It returns always to login window

[Maik (voody13)]

I have the same problem. I had 11.10 installed, updated to 12.04 and now I'm not able to shut down the system any more. The "ubuntu-screen" appears and nothing more happens everytime I try to shutdown. I also can't get my network card working. So I installed 12.04 complely new to ensure it was not a problem of the update and got the same results. With 11.10 and Win7 everything is working fine.
(System: Desktop "MSI Hetis 945-E", Intel E4500 64bit, 4GB Ram, Win7 64bit, 12.04 64bit (before: 11.10 64bit))

[Bernhard Graaf (bernhard-graaf)]

The same for me with XUbuntu 12.04 on 3 different systems (Dell, Asus-Notebook and self build system).

[Bernhard Graaf (bernhard-graaf)]

Sometime it works with command: shutdown now -h
It never works with command: halt

[Michael Kogan (michael-kogan)]

I encountered the problem on another system. Both systems using fglrx, the first time that the problem appeared was right after the installation of fglrx.

[j-stuffer (j-stuffer)]

I also think that fglrx could be the reason. (fglrx is the proprietary driver from ATI, right?)
I removed the driver and I had no problem with the shutdown. But as soon as I installed it again, I wasn't able to shut down again.

But I only started / shut down the laptop about 5 times without fxglr, as I usually use my desktop and also not using fglrx works not very well for me as:
1.) fan runs a lot more
2.) battery runs a lot less longer
3.) I can't switch users

[Bilal Akhtar (bilalakhtar)]

Seems like an issue with Upstart.

[Mark Schneider (mc-monti)]

I am afraid that different incidents are mixed together here. As far as I understand in some cases the system remains in the process of shutdown. In other cases the shutdown of the operating system seems to work except the very last step of turning off the hardware.

[Andre (ajx)]

I really wonder why people post comments stating they "are affected too", and don't click on "Does this bug affect you?" at the top of the page. Only stating that you are "affected too" this way will draw more attention to this bug. I've counted 6 comments, but only 4 votes.

I'm experiencing the problem occasionally on Lenovo Thinkpad X220. The system basically goes to halt, but doesn't switch off the laptop. I have to long-press the power button to switch it off. During the next reboot, I don't get a filesystem check - what makes me think that it was umounted properly.

In what log files can I check what the problem is? And what to look for?

[Andre (ajx)]

I experienced the problem now also on another machine which I tried to shutdown via "sudo halt". Shutdown seemed to be OK, but the PC (desktop) was not switched off. I didn't experience this problem on Oneiric. It was introduced after the upgrade to Precise Pangolin.

[Mark Schneider (mc-monti)]

I noticed something in the past days. If I click shutdown the screen normaly turns black very fast. It does not show "Ubuntu" with the four dots, and at the end of the process I have to turn off the computer by pressing the power button a long time.
The few times I see the screen with Ubuntu and the four dots the shutdown works fine.

[Andre (ajx)]

I can see the dots moving. However, they keep on moving, but the device is not turned off.

[Mark Schneider (mc-monti)]

I also found out that after some time of using Ubuntu I can't switch to a terminal session anymore. Using Strg-Alt-F2 for example does not work after a while. The screen turns black and that's it. Pressing Strg-Alt-F7 brings me back to Unity again.
The shutdown works fine as long I can switch to a terminal. If I can't the shutdown does not work either.

[Andre (ajx)]

That's a very intersting observation, Mark. Thanks! I'll keep an eye on that, i.e. check if I can jump to another TTY before I shutdown.

On my laptop (Lenovo X220) I have noticed that the indicator lights (LEDs) for wifi and power(!) turn off, while the screen stays on. Marks observation plus this one points in the direction of problems with the graphics driver. My graphics card is Intel. Should be a GMA 3000. lspci says:

VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)

[Andrius Preimantas (andthreep-deactivatedaccount)]

I have Dell Inspiron 1520 and Ubuntu 12.04 fresh install, and it also doesn't completely turns off. Have to force the shutdown by holding the on button.

[Vova U (uwl)]

it's not only a notebbok related issue i see the similar behavior on MSI H61M-P22(B3) mainboard. The the screen will be turned off but the CPU fan will be slowed but never going off. I tested this with booting from Ubuntu 12.04 distribution DVD and and Try Ubuntu. Both power off just after start and power off after 30 min playing with firefox and libreoffice just powering the system off completely. Probably some regression during recent updates?

[[e-mail] (rsw)]

Using a Dell D530 with NVIDIA graphics card. Same problem and any solutions I have tried have been infrequent.

[Mark Schneider (mc-monti)]

Is anybody experiencing the same problem with Kubuntu 12.04?

[Lalatendu Mohanty (then4way)]

I have the same issue in my Dell 12.04 . But I have observed that if I turn off the wireless and then shutdown , it works fine. Also "sudo poweroff" also works for me.

I have installed "firmware-b43-lpphy-installer" for my Wireless card as its Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] card

[anders (anderspn)]

I have the same problem on my Dell Inspiron 1720. Everything appears to shut down except the fan and leds which stay on.
Also I have noticed problems with the wireless network.
If I turn on my wireless router after Ubuntu has started the network newer connects. The workaround is to disable and
reenable the network.

[Steve Langasek (vorlon)]

> Sometime it works with command: shutdown now -h
> It never works with command: halt

That refers to bug #880240, which is not the bug reported by the submitter. The 'halt' command does not do what people assume it does. You need to call either 'shutdown -h now', or 'poweroff', or 'halt -p'.

The bug here is with the system not shutting down when shut down from the GUI - that's not at all due to a user calling the wrong command from the commandline. Perhaps the GUI makes the same wrong assumption and calls 'halt' when it should not, or perhaps there's a hardware-specific issue with the poweroff handling. (This would not be the first time that had happened, but most such problems were long ago with a much less mature kernel.)

[Steve Langasek (vorlon)]

indicator-session calls the consolekit shutdown interface, which uses '/usr/lib/ConsoleKit/scripts/ck-system-stop', which calls 'shutdown -h now'. So it doesn't look like there's any indicator-session bug here.

[plum7500 (plum01)]

Shutdown using menu is working for me but using the terminal does not. If I do

sudo shutdown -h 2:00

to shutdown at 2am, it hangs. Another thread said that it does not happen if root user is used. I'll post later if root is able to do it successfully.

[anders (anderspn)]

I can confirm that changing to the virtual terminal also stops working. This may be caused by the binary nvidia driver for
the GeForce 8600M GT graphics card in my PC. I am currently using version 295.49 of the driver but both installed
drivers have the fault. I have used Ubuntu on this PC for several years without this problem so this bug was
introduced with 12.04.

I have tried "$ sudo poweroff" from a terminal and it fails. Shutdown from an remote ssh login also fails. Currently I do not have
any safe way to shut down the system.

[Michael Kogan (michael-kogan)]

It is surely not related to gnome-session, since the problem also appears on Xubuntu Precise.

[Jordan Roszmann (jordan-roszmann)]

I also have a GeForce 8600 GT. I recently reverted to version 290.10 of nvidia's binary driver because of Bug #973096 (random Xorg crashes.)

The reversion also seems to have solved my problems powering off the system and changing to tty. It might be a coincidence, though.

[Mark Schneider (mc-monti)]

Did you try the current verson of the NVIDIA-driver 295.59 as well?

[plum7500 (plum01)]

Running the following as root works but not as regular user using sudo:

shutdown -h 2:00

I have an AMD graphic card. Hope that helps in debugging.

[Mark Schneider (mc-monti)]

The new headline is not really correct. It does not only happen when chosen "shut down" from gui, it does also not work if I type "shutdown -h now" in a terminal.

[Jordan Roszmann (jordan-roszmann)]

Version 295.59 did not resolve the X crashes for me, so I went back to 290.10. I did not notice if version 295.59 resolved this issue.

[Lino Sison (linosison)]

I have no solution, but want to list my equipment, just in case it matters: Dell Poweredge SC 440 and NVidia GE Force 6200 (PCI) video card.

[Mark Schneider (mc-monti)]

The circumstance that I can't switch to a terminal session with Strg-Alt-F2 after a while starts to bother.

[Charles Jie (chjie)]

I have the same problem on 6 notebooks in my recent installation of ubuntu 12.04 desktop (either amd64 or i386).

Three are mine:
Toshiba L640 (i3 box with amd/ati video chip, amd64)
acer aoa150 (netbook)
acer aod150 (netbook too)

Three are on my 3 students:
asus (netbook)
asus UX31E (i5, new slim notebook, amd64)
acer MS2346 (i5, new slim notebook, amd64)

Because we seldom (it does succeed sometimes) succeed to shutdown from system menu, now we all rely on <alt-f2> sudo poweroff, which is sure to turn off it.

p.s. If it fails to finish, it will stay at a high level of power consumption, e.g.
  My toshiba L640, it will go from 22W to 35W
  Asus UX31E, it will go from 17W to 29W.

[Charles Jie (chjie)]

In addition, the ubuntu 12.04 installation iso (i386 or amd64) can't shutdown either:

I put the iso in a flash drive: boot by grub4dos, fat32 fs, with casper-rw to save changes.

I've used these flash drives (one for i386, one for amd64) to install many laptops (more than 10), but I can never shutdown after finishing installation. (So I always have to repair the casper-rw file system afterward.)

[Kris Marien (kris-marien)]

I have a netbook with Intel Corporation Mobile 945GSE Express Integrated Graphics Controller.

I started having poweroff issues after adding the ppa:xorg-edgers to my repostiitory.

This ppa installs as a complete package with all elements in it.

Hope this info will help.

[Stefan Essl (stefan-essl-vhs)]

I've installed Linux Mint 13 (Maya) Ubuntu 12.04 based on 6 PCs for educational purpose.

Shutdown via GUI does not work at all. The PCs remain powered on, but no input is possible....

I tried to turn them off on a console but only one manages to power off after
    :~$ sudo shutdown -h now:~$
but not always...

The others show the line
   [876.9876] Power down.
forever until i turn them off manually....

After googling around I've found the kernel parameters
  noapic nolapic acpi=off
...but it didn't change the problem really, sometimes it worked, sometimes not...

Then I read the posting from
  plum7500 (plum01) wrote on 2012-06-13:
and i tried:
    :~$ sudo su -
    :~# shutdown -h now

I use kernel 3.2.023
The PCs have nvidia cards...could this be the problem?

I tried to switch from "nvidia current" to "nvidia current-updates" on one PC:
After restart i tried to turn off via GUI and it did not power down...
I tried again as root on the console, the PC had noapic and nolapic options as kernel parameters:
Ctrl-Alt-F1 => console
loggedin as user
    :~$ sudo su -
    :~# shutdown -h now
...and it did shutdown....

All PCs used to power off since Ubuntu 8.04 ....what can I do? BIOS ACPI settings?

[Stefan Essl (stefan-essl-vhs)]

...on next reboot I tried turn off again as root, but then it didn't work....

this is not funny...it reminds me on another OS I've used to struggle with on decade, and I'm happy that I nearly have anything to do with it!
...and of course I'll never be using that again! LINUX 4ever!

[Stefan Essl (stefan-essl-vhs)]

...also no poweroff after shutdown -h now in runlevel 1!....
kernel issue?

[Rohan (rohantn)]

I have the same problem. I have a compaq presario 2109 laptop with an AMD Athlon processor.

If I shut down, the screen freezes with the ubuntu home page with 4 dots and the dots don't move. I have to manually power off.

If i try shut down -h, that doesn't work properly either.

[Stefan Essl (stefan-essl-vhs)]

upgraded two systems:
     :~$ sudo apt-get update; sudo apt-get upgrade ; sudo apt-get dist-upgrade

After restart shutdown as user worked with final power down!

Now I have kernel
3.2.0.25

Upgraded without any issuses!

I'll try the other PCs and tell you if it also worked...

best wishes
stefan

[Stefan Essl (stefan-essl-vhs)]

so all 7 PCs power off finally!

SOLUTION (in my case): upgrade to new kernel 3.2.0.25
[see last post]

Thanks to all error-reporting people, so problems can get solved!

Happy day and a long life!
stefan

[Stefan Essl (stefan-essl-vhs)]

...too early...
4 PCs stuckk at power down....
:-(

tomorrow i'll be after it again...

[Michael Kogan (michael-kogan)]

I think, whoever is able to, should set the importance of this bug to "high" since it affects many people and is quite an important issue.

[Stefan Essl (stefan-essl-vhs)]

First testrun today:
2 PCs never powered off after shut down
- with noapic,nolapic
- without noapic,nolapic
always with sudo su - as root
shutdown -h now

sudo shutdown -h now
didn't power off.

GUI shutdown directly from login screen power off. tested once...

1 PC powered off from GUI shutdown directly from login screen once,
 but tested it again it waited with "power down" line....
This one didn't power down with
sudo shutdown -h now

4 PCs powered off after shutdown via
sudo shutdown -h now

but didn't shut down as root with
shutdown -h now
and also not in runlevel 1...

So it seems to me that if I'm lucky it powers off...
this can't be real...

thinking and hoping for solution
stefan

[Stefan Essl (stefan-essl-vhs)]

so i googled around again and found the following:
https://bbs.archlinux.org/viewtopic.php?id=113985&p=2
I know, another distro another kernel.
But it is quite the same phenonemon.
https://lkml.org/lkml/2011/4/4/121
is a report about some kernel issue, which maybe could be the cause...

I tried:
laptop-mode-tools weren't installed on my PCs
So I installed it on 2 PCs.
After restart one powered off after shutdown via GUI the other didn't.

I removed laptop-mode-tools on the PC were it didn't work and restarted:
Now it powered off after shutdown via GUI.

Now I tested shutdown again and one powered off after shutdown via GUI the other where I installed and removed the laptop-mode-tools did not power off after shutdown via GUI.

so....

[Stefan Essl (stefan-essl-vhs)]

...and the third time I tried to shutdown the PC with laptop-mode-tools installed, did not power off after shutdown via GUI....

so this is a kind of russian roulette? new kernel feature? ;-)

a little bit desperate

stefan

[setcho (setcho)]

Shutdown hangs on the Ubuntu 12.04 shutdown screen and does not turn off. A couple of things to note:

1. This problem does not happen all the time. Approximately, for every 4 shutdowns 1 will work and 3 will hang and not complete. The Ubuntu shutdown screen does not display correctly on the 3 failures. "Ubuntu" appears larger than it should and there are no progress dots below it. On the one shutdown that completes "Ubuntu" appears at the right size on the shutdown screen and the progress dots are working.

2. This error coincided with the death of my Graphics card, I have no idea if they were related it was 4 years old so it could have been just normal wear and tear. Anyway whilst I waited for my new card I installed Xubuntu 12.04 on an old Dimension 3000 with integrated graphics, all shutdowns completed correctly. Recieved new graphics yesterday and reinstalled Ubuntu 12.04 on my main machine and shutdown problem persists.

Specs: Dell XPS 420 using fglrx originally on a ATI Radeon HD3870 now on ATI Radeon HD5450.

[Stefan Essl (stefan-essl-vhs)]

Day 3:
Yesterday I did a BIOS configuration on 2 PCs: I told BIOS to load the
optimized defaults
and
saved (F10) the configuration.
The 2 PCs were the 2 were I tried the laptop-mode-tools, which worked as described above...

Now after saving the BIOS settings, I tried today 3 times to shut down and power off the PCs and...
SURPRISE it worked!!!

I tried it in the GUI and the first time
- immediatly after login => powered off!
- waiting a little bit and shut down without login => powered off!
- and last test was: logged in started an application (firefox, libreoffice) waited about an hour and then shut down => powered off!

So 2 PCs now seem to work.
I will try it (BIOS default settings) with the other 5 PCs and will report my expierience.

Best regards
stefan

[Stefan Essl (stefan-essl-vhs)]

Tested all 7 PCs with the default BIOS Settings:
- all turned off via GUI not logged in => powered off!
- all turned of via GUI logged in and all had an application running (firefox) and they were powered on for about an hour => powered off!

Tomorrow i'll test them again, and hopefully all will power off as they should!

Maybe this can help anyone with similar problems...

Best regards
stefan

[Michael Heyns (mike-bean-heyns)]

I've had this problem with 12.04 for a while. Had no idea what caused it. Found a fix in ubuntuforums renaming priorities in upstart scripts but never bookmarked the thread(12.04beta)

Struggled on recent install until I noticed reboot/shutdown worked when dropping to tty1 and stopping lightdm service. I have updated my AMD graphics driver to Catalyst version 12.4 and so far everything is back to normal, including plymouth.
Will see if it persist.
--
Radeon HD 6700 Series ; i7-2600 ; H67 Express Chipset
Linux bean-desktop 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[Stefan Essl (stefan-essl-vhs)]

Last Day - final test after "loaded optimal BIOS defaults":

first of all: YEESSS, they did all shutdown and power off without any hazzle! Hooorrrraaayy!!

what and hoe did i test:
starting at 9 a.m. i turned on all 7 PCs and logged in.
9:15 i shutdown the 1st and it did power off.
11:00 2 PCs had firefox running nearly 2 hours and then i shut them down and they did power off.
1 p.m 3 PCs had firefox and libreoffice running and then i shut them down and they did power off.
3 p.m. 1 PC had firefox and evince running and then i shut it down and they did power off.

so no matter how long they ran, it was possible to shut them down via GUI and they powered off.

This is what they also did with Ubuntu 8.04....
So something must have changed and it has to do with the BIOS settings and the kernel....
but i don#t know what exactly...

Hope you all have a nice day and i hope the PCs have learned their lessons ;-)

Best regards from vienna, austria with nearly 100 deg. Fahrenheit

stefan

[anders (anderspn)]

Great work!

This also solves the problem on my Laptop: dell Inspiron 1720 (Intel Core 2 Duo T7500, Nvidia GeForce 8600M GT)

I did the following:
1) reboot and enter BIOS setup by pressing <F2>
2) use menu: [+] Maintenance -> * Load Defaults

After this I re-enabled virtualization support because I occasionally use virtualbox:
3) use menu: [+] POST Behavior -> * Virtualization

Both virtual console (ctrl-alt-f1) and power down is working now. Don't know what caused the problem in the first place though.

Best regards
Anders

[anders (anderspn)]

Ups don't think it solved the problem. Ctrl-alt-f1 has stopped working now. Apparently it only works right after power-on

[Mark Schneider (mc-monti)]

Changing to default values did not help me either. I tried so many things in the past weeks but I can't make it reproducable or find any more coincidences.

[Michael Kogan (michael-kogan)]

I think, it could be a matter of what defaults the motherboard manufacturer uses in each case.

[Mark Schneider (mc-monti)]

I do not think it's a BIOS-issue in my case. I will keep on testing.

[Mark Schneider (mc-monti)]

I found out something interesting:

I installed the KDE-environment via software center. I observed the following behavior:

I always can work in Unity, I only can't switch to a tty after some time. If I use KDE, I work normally, but all of a sudden my entire system freezes. I also can't switch to a tty anymore. I think at the point where I simply can't switch to a tty in Unity anymore, the KDE-System freezes.

[Mark Schneider (mc-monti)]

Sorry, I was wrong. KDE is still working while I can't switch to a tty.

[Stefan Essl (stefan-essl-vhs)]

Hi comrades,
   PCs seem to have learnt their lesson ;-)

They shutdown and poower off.
Ctrl-alt-f1 works. also the other consoles work. On some machines with a little lag but it works.

@mc-monti: your problem seems to me very hardware-specific. Can you disable ACPI in BIOS?
Did you ever had a distro which sut down and power off regularly? If not, it will be hard to find a solution, because then it is for sure a hardware-specific phenonemon...

best regards
stefan

p.s.: nice weather in vienna,austria! cloudy and cool 23 deg Celsius.

[Mark Schneider (mc-monti)]

@Stefan
My last distribution was 10.04 LTS and it worked perfectly. This problem occured with 12.04.

[Stefan Essl (stefan-essl-vhs)]

@mc-monti: then there is a way how it can work, so we only have to find it!
Are there any energy (ACPI) options in your BIOS, which could be adjusted?

[Mark Schneider (mc-monti)]

No, there are no changes possible.

How could a BIOS issue cause that I can't switch to a terminal after a while?

[Stefan Essl (stefan-essl-vhs)]

I experienced similiar problems when notebooks (their CPU) are getting hot:
- the machines stuck / freezes and i wasn't able to do anything.

Machines got hot when the power management didn't work as expected...and the problem was the ACPI or APM configuration/manipulation in BIOS (if there was any possibility at all) or in the kernel...and things got better and started to work with ubuntu 8.04

The great problem is, so do i think, that there are many hardware vendors, and they all have different components from different manufacturers and they all have different BIOS Software and not all have the time to stick to conventions/norms/standards or they don't like the standards....but it is really hard to find out, if it is a real hardware damage or a workaround, with which one could live...

In your case there must be a solution, because it worked with 10.04 LTS, so it has to work with 12.04 LTS too.
Maybe there was a certain/extra kernel module in10.04 in use for your notebook, which made it work as expected?

[Mark Schneider (mc-monti)]

It worked out of the box without any modifications and I did not load any additional modules. Chances for a hardware damage are very low since other users seem to have the exact same problem.

[Stefan Essl (stefan-essl-vhs)]

don't know if this is really useful, but it shows that the problem is not OS dependent.
http://www.insanelymac.com/forum/index.php?showtopic=192864

What I read there is that there is an issue about the nvidia card driver and the kernel.
So maybe if you just use a generic driver, it could solve your shutdown - poweroff problem, but you won#T use the nvidia driver, what could be but maybe is not an issue...
But it is just another guess!

...yes of course also other users have an similiar but maybe a slightly different problem...and as we said before: it worked with 10.04 so it will with 12.04!

[Mark Schneider (mc-monti)]

Ok ok, I'll share your optimism :)

I already experimented a little with the nvidia driver. I switched to current updates. I am running now version 295.49. It did not help. I will try to install a generic driver and report then again. But first I have to find out where to get a generic driver :)

[Mark Schneider (mc-monti)]

I removed all the nvidia stuff. My first impression: Wow, everythin is much faster than before!

[Mark Schneider (mc-monti)]

@ Stefan

I won't count my chickens before they hatch ... but removing the nvidia driver seems to solve the problem. I started and restarted my notebook very often after switching to the generic driver.

I can't believe it. I will keep on testing. And I also will test new drivers.

But so far: THANK YOU!

[jkbkot (jkbkot)]

I'm experiencing this bug on my T420 without Optimus. There is no nvidia stuff on my system so removing the nvidia driver maybe solves the problem only for someone.

[Angel D. Segarra (angel-segarra)]

I was sufferring from this, eventually installed Xubuntu 12.04 and all was well

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/987933/comments/8

If anybody else goes this route please let us know if you are still affected. In my case I can shutdown and reboot without problem and using any driver, nvidia-current and nouveau.

[Matt (mdegrave1022)]

HI All,
From what I have read there seem to be several problems within this thread. I am having the same issue as originally stated. When powering down or restarting the system seems to hang, the operating system shuts down but the hardware never turns off.

I am running Ubuntu 12.04 LTS on a Dell D630 core duo. I have 2GB of Ram and I am running Nvidia graphics. I have gone into the BIOS and disabled all unnecessary hardware( modem, bluetooth and a few others)

As a side note upon the original installation of the OS the shutdown and restart worked fine. The problems did not start until the second update of the operating system. Then it would not restart properly, then the third or fourth update the shutdown would not work properly.

[Mark Schneider (mc-monti)]

Did you try to switch to a generic graphics driver?

[Matt (mdegrave1022)]

I removed

Nvidia accelerated graphics driver (version current)[recommended]

NVIDIA accelerated hraphics Driver (post-release updated) (version current-updates)

I am now completely free of proprietary drivers and so far it seems to have worked. I rebooted twice and it the problem was not there.

Now the question is what in the drivers is causing the problem.

[Stefan Essl (stefan-essl-vhs)]

@mc-monti:
I am happy that it finally worked for you!
...and that everything is faster too!

Btw. recently Linus Torvalds made a statement about nvidia...
http://www.heise.de/newsticker/meldung/Torvalds-zeigt-Nvidia-den-Stinkefinger-1619616.html

best regards from rainy vienna, austria
stefan

[Mark Schneider (mc-monti)]

@Stefan
I already read the article before. :)

I never had any problems with the driver before. In fact I used to have more problems with the generic driver so I always installed the nvidia driver right after setting up the system without giving the generic driver a chance again.

Now I am curious to know what the pros are for the nvidia driver.

Best regards from rainy Berlin, Germany :)

[Peter Liebe (petliebe)]

@Mark no - removing nividia driver is not solving the problem. I have done this with no effects at all. I can't still shutdown properly.......so I think this is severe and should get a higher priority.

[Mark Schneider (mc-monti)]

@Peter
That's because you probably do not have the same problems like I described in my starting post.
Removing the nvidia driver already helped others who had the same problem. All those who's system behavior differs from the described one should open another bug report.

[[e-mail] (rsw)]

I agree with Peter, removing the driver did nothing for me. I still cannot shutdown also.

[Nicolas Jungers (unbug)]

I've at least 3 ubuntu 12.04 setup that cannot poweroff on shutdown:

1) iMac Alu 24" with ATI board and fglrx driver
2) ASrock MB with AMD E-350 and 12.04 server
3) VirtualBox 4.1.12 machine with 12.04 server

[Nicolas Jungers (unbug)]

Oops,

After reading the difference between halt and poweroff, I have to withdraw my comment. poweroff works indeed on the server. But previously, halt without the -p option did a poweroff to.

[j-stuffer (j-stuffer)]

For me the problem is solved, it seems. The last times I shut down my laptop it always worked.

[Marcelo Ruiz (marcelo-javier-ruiz-yahoo)]

I started experienced this problem with the mainline kernel 3.4... Maybe that helps. I am uploading system info via apport...

[druss (druss)]

I have the same issue. When I shutdown my PC via GUI the "ubuntu-screen" appears and nothing more happens. But this bug can be reproduced only if Opera browser open during shutdown process. If I close Opera before shutdown PC, it power off successfully.
P.S. I also have fglrx driver installed.
P.P.S. "sudo shutdown -P now" always work fine.

[Aftab Yousuf (aftabyousuf)]

I have also tried Linux Mint Maya and I found this same problem in that also. Then to check I installed Fedora 17 and opensuse 12.1 they both are working fine. I dont know why Ubuntu and distro based on it are having this problem.

In my view this is the problem related to ubuntu core system or might be debian.

[Joshua (joshua-immanuel)]

The problem occurs both in Fedora 17 and Ubuntu 12.04. Sometimes there is a clean shutdown but most of the times it doesn't power-off the system. Keyboard and network card (green light indication on the ADSL router/modem for this wired line turns orange) is turned off, but cpu fans, power and hdd led's are in ON condition. I have to manually (long) press the power button to turn off completely.

[F. Aly (f-aly)]

BUG: unable to handle kernel paging request at ffffc9000253c00
IP: [<ffffffffa0682ef4>] firegl_sig_notifier+0x4/0x40 [fglrx]
PGD lib41a067 PUD lib41b067 PMD 1150f4067 PTE 0
Oops: 0000 [#2] SMP
CPU 1
Modules linked in: fglrx(P) dm_crypt joydev rfcomm bnep bluetooth (...)

[last unloaded: fglrx]

(...)

Watchdog detected hard LOCKUP on cpu 1
---
This is what I see when shutting down. Seems to me like a kernel bug in properly unloading the proprietary grafic drivers.

[Lucy O'Neill (glassempire)]

In my case - uninstalling all proprietary NVidia drivers solved the problem (Dell XPS M1530) but have to put up with rather crappy graphic; SMPlayer doesn't work and launcher & icons pretty big (it can be fixed though) - but at least system shuts down no problem and it was the aim.
We just have to be patiens i suppose and wait for a final solution.

[anders (anderspn)]

Is it confirmed that the power down hang problem is caused by the nvidia driver.
The reason I ask is because I also have issues with wlan on my PC.
If I turn on the router before booting ubuntu the network newer connects. I then have to "disable network" followed "enable network" before it works.
Sometimes it connects but does not seem to be configured correctly. I used to be able to run "sudo /sbin/dhclient" in previous ubuntu releases but in 12.04 this command just hangs.

[Etai Sandow-Vandel (itay-vandel)]

For me the problem seems to have been resolved after removing fglrx, so I'm
not sure the problem is the nvidia driver (as I have an ATI card).

[Michael Kogan (michael-kogan)]

I suppose that it's due to _some_ proprietary driver being installed, no matter which one.

[Lucy O'Neill (glassempire)]

Hi again, just by accident found on some foreign ubuntu forum solution that might be checked out; i have to leave right now so cannot play with it - but if someone wants, feel free to try.
They say it's acpi issue and it has to be switched on in GRUB
GRUB_CMDLINE_LINUX="acpi=on"

sudo update-grub

they maintain that it works on Dell laptops

[John Need (john-need)]

Lucy O'Neill's a genius. Her fix worked for me. I'm running a Dell Inspiron 1720 with an NVidia card. Here's what I did

gksudo gedit /etc/default/grub

Replaced e the line GRUB_CMDLINE_LINUX="" with GRUB_CMDLINE_LINUX="acpi=on" and saved the file

sudo update-grub

Rebooted (I had to hold the power button)

Shutdown (Did not have to hold the power button)

[Lucy O'Neill (glassempire)]

Lads - this is NOT my solution, just found it browsing other potential sources.
It comes from polish Ubuntu forum. Topic was closed so i presumed they've sorted it out.
I'm so glad it works, soon will try on my own XPS M1530.

[John Need (john-need)]

Nonethess, kudos for the legwork.

[anders (anderspn)]

This does not have any effect on my dell inspiron 1720. After a while the virtual consoles stop working (ctrl-alt-f1) and it is
then no longer possible to shutdown or reboot without pressing the power button.

[Lucy O'Neill (glassempire)]

At last tried it myself and - with NVidia proprietary driver back installed - problem is present. The solution i've got seems not working for me neither.
So i suppose it does work in some cases - but is not (and shouldn't be treated as) solving the issue for everyone.
For now i don't have NVidia installed and things are fine, graphic improved a little with recent updates. So we may not need proprietary drivers at all in the future, being fully replaced by system default ones.
But it doesn't mean that we're defeated - there MUST be some way to fix it!

[louBurnard (lou-burnard)]

I have this bug on a thinkpad x301 since upgrading it to Pangolin. It's intermittent though -- occasionally choosing Shutdown from the system menu (top right) has worked but usually it just hangs on the "ubuntu" splash screen with the little row of white buttons flashing red. LEDs show that wireless is off, but not power. And the laptop gets quite hot unless I force it to shut down with the vulcan nerve pinch.

No NVIDIA drivers here.

[Vova U (uwl)]

dear anders

why do you mean "Is it confirmed that the power down hang problem is caused by the nvidia driver." as you wrote? If you take a look at this discussion you can see, not only nvidia systems are affcected. I see the same behavior on MSI H61M-P30 (B3) with Sandybridge Desktop (GT1).

[anders (anderspn)]

I was just hoping that we could identify the root cause of the problem, but perhaps it is not so simple or maybe there is more than one bug.
In my case I removed the closed source nvidia driver yesterday as suggested by Lucy O'Neill. The procedure is described at the following homepage: http://nouveau.freedesktop.org/wiki/UbuntuPackages
The open source nouveau driver is working fine and the system is now able to power off without problems.

[Michael Kogan (michael-kogan)]

As I already wrote multiple times, it looks like the cause of the problem is _a_ proprietary graphics driver, no matter which one. So you're both right in some way. :)

[anders (anderspn)]

I guess Linus Torvalds is right in his opinion about nvidia. It is pretty hard to debug and fix a problem when you don't have the source code. http://www.youtube.com/watch?v=_36yNWw_07g

[Vova U (uwl)]

Hey Photon
if you are right, starting the system without X will solve this problem. Looks like an interesting ideal! I'll try this tomorrow.
We discussing probably several issues with similar behaviour. Is it one bug or several is only a question of definition. One thing is definitely known, after the update from10.04 to 12.04 several systems don't power off any more. It's not known which kind of systems is affected. From 5 PCs with 12.04 near me only one system is affect, one of these PCs uses nvidia proprietary graphics driver and it is *NOT* affected. Another one has a nvidia graphics with nouveau driver. I tested this by install and uninstall of proprietary graphics driver and can't reproduce this issue. Two Lenovo laptops are not affected, no nvidia graphics. One of this laptops has similar graphics as the affected PC. But why this PC can't shutdown? Probably damages nvidia driver something in ACPI or making something else what can cause this issue, but it can't be a root cause. We probably need to collect more information about affected systems. Then we hopefully know how to reproduce this issue.

[anders (anderspn)]

I am now using the nvidia driver again because the PC gets very hot when using the nouveau driver (power management is not implemented so it always runs at 100%).
It appears that the shutdown issue is only present in version 295.49 of the nvidia driver. Version 173.14.35 is working but has other issues regarding resume from suspend and changing from console to X (ctrl-alt-f7).

[Vova U (uwl)]

it's abit difficult to reproduce, directly after the reboot poweroff powers the system off. The system can't power off just it was used. Simply login into the unity session and then poweroff doesn't reproduce this issue. any ideas?

[narea92 (arena-g)]

If I remove 'Kalarm' my PC (AMD64) works fine.

[Daithi O'Coinnigh (c4u6tu)]

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: david 1768 F.... pulseaudio
 /dev/snd/pcmC0D0p: david 1768 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 44'
   Mixer name : 'SigmaTel STAC9205'
   Components : 'HDA:838476a0,102801f1,00100204 HDA:14f12c06,14f1000f,00100000'
   Controls : 21
   Simple ctrls : 12
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=ad1c9911-6fd7-40e3-a884-df59633026cd
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: Dell Inc. Inspiron 1520
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae root=UUID=b6e74791-61dd-4e9c-b738-8363392ebb60 ro quiet splash acpi=force vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-29-generic-pae N/A
 linux-backports-modules-3.2.0-29-generic-pae N/A
 linux-firmware 1.79
Tags: precise running-unity precise running-unity
Uname: Linux 3.2.0-29-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/16/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0UW306
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/16/2007:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn0UW306:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1520
dmi.sys.vendor: Dell Inc.

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Daithi O'Coinnigh (c4u6tu)]

apport information

[Oleksii Melnychuk (melnitschuk-o)]

I had the same problem at my Dell Vostro 1500 with NVidia GeForce 8400M GS with both nvidia-current driver and latest driver from NVidia official site. The problem was solved for me using nvidia-current driver by disabling PXE-boot ability for LAN at BIOS. If somebody has Wake-on-LAN (WOL) setting (Dell Vostro 1500 doesn't) - try to disable both PXE and WOL. Hope this will be helpful for somebody.

[kschsch physik (kschsch-physik)]

Same problem for me:
Linux ivypc 3.5.1-030501-generic #201208091310 SMP Thu Aug 9 17:11:48 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 12.04.1 LTS \n \l
Have to do halt -p instead using the menu button.

[j-stuffer (j-stuffer)]

The last times that happened to me, I had opera open when I shut down. Only a wild guess: Maybe it has something to do with flash?

[j-stuffer (j-stuffer)]

Ok, now I'm quite sure this happenes to me, when opera still runs while I try to shut down the computer. When I close opera before, it works.

(P.S. Some time ago, I think the computer did not shut down, even though I had closed opera. But this seems to be fixed now, It seems)

[Vova U (uwl)]

during of rummage through MSI forum, people complaining already 2008 about shutdown problems not under Linux. it's advised to try to disconnect external active USB hub and connect all of USB equipment to onboard USB portst or not to use a USB hub power supply. during my last tests i disconnected most of USB devices but never tried to disconnect a USB hub itself. today i removed the power from the hub and connected all USB things but DVB-T stick to onboard ports and the problem is gone. don't understand why this buggy(?) hub didn't affect the shutdown process under 10.04 but 12.04...

[narea92 (arena-g)]

Ubuntu 12.04, (also Ubuntu 12.10 Alpha), does not shut down if KAlarm is running. Instead of shuting down, a message appears sayng that a program is still running. If I have not KAkarm runnig, the PCm (amd64 powered), shuts down properly.
Gaetano Arena

[lvelden (l-j-j-vandervelden)]

setting acpi=force in the commandline options of 'etc/default/grub', solved it for me. My system missed only the last step of motherboard powerdown.

[lvelden (l-j-j-vandervelden)]

see previous comment, problem persists, although not as frequent

[Charlotte Corday (charlotte-c)]

I have the same problem. My computer is a Dell Inspiron 1420, with Ubuntu 12.04 (32 bit) and Nvidia GeForce 8400M GS graphics card (I'm using the recommended drivers).

[Ben (ben-lemire)]

Charlotte's updated description is an exact match to what I am experiencing on my ThinkPad T61 with the recommended Nvidia driver.

Card: Quadro NVS 140M
Driver Version: 295.40-0ubuntu1.1

[Gustav Andersson (6-gustav-q)]

I have the same bug, Ubuntu 12.04 running MacBook Pro Retina, installed NVidia drivers (specifically CUDA 5 driver). This is my experience:

first a general observations: I have another bug which may be related to this one: ctrl alt f1 only gives me black screen (but ctrl alt f7 gets me back)

1. booting in 'text acpi=force' mode (instead of 'quiet splash'):
shutdown works correctly (-h -r -P all works)

2. booting in 'text' mode without acpi=force
shutdown doesn't power off the computer

2. booting 'quiet splash acpi=force'
shutdown doesn't power off the computer

[Gustav Andersson (6-gustav-q)]

I was able to get shutdown to work correctly by booting with 'nomodeset'. It turns out I do not need acpi=force so this is all I need in /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic nomodeset"

and it works. (I still have the ctrl alt F1 problem though)

[Jay (jfjanssen)]

At http://askubuntu.com/questions/125844/shutdown-does-not-power-off-computer I found the following suggestion:

________________________________________________________________________
Type in terminal:
1. sudo gedit /etc/default/grub
2. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
3. Change this to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force"
4. Save the file and close the file. 5. Finally, in terminal: sudo update-grub
________________________________________________________________________

This works for me. Still, this is a workaround; for Ubuntu to be found atractive for non-power users, the system should shutdown without having to edit system files. A solution where this situation is auto-detected on affected systems and then fixed would be nice.

[Jay (jfjanssen)]

In Comment #154 I reported that the suggestion I found at http://askubuntu.com/questions/125844/shutdown-does-not-power-off-computer worked for me. Sadly, I now have to report to I concluded that too soon; it does not work.

[anders (anderspn)]

Hi,
Yesterday I upgraded from 12.04 to 12.10 and this appears to solve the problem.
The reboot after the upgrade worked and the PC was able to shut down and power-off yesterday.
I will report back if the problem pops up again.
Best regards
Anders

[John Need (john-need)]

I am happy to report that the upgrade to 12.10 has fixed this problem for me.

[Orosz Gyozo (oroszgyozo)]

I don't want to upgrade to 12.10, "halt -p" and adding "acpi=force" does not work, also I am not able to switch to console mode ( Ctrl + Alt + F X ). My laptop is a Dell Latitude D830 with Quadro NVS 140.

[Charles Kerr (charlesk)]

indicator-session is just a user-visible way to trigger the "Shutdown" message on DBus.

Given that the OP is reporting that the shutdown is initiated (even if it doesn't complete), indicator-session's done its job.

[Fwunix (fwunix)]

I'm having this problem on Kubuntu 12.10.

I didn't have it on Kubuntu 12.04.

[j-stuffer (j-stuffer)]

Seems for me opera (perhaps flash plugin?) is in deed connected to my problems in shutting down the PC.
The last two times I could not shut down the system, after I rebboted and started opera, opera told me that opera crashed and if I want to continue the session. But prior to shutting down I always closed opera and shut down the system shortly after.

[Karma Dorje (taaroa)]

Please don't change this bug's status without an explanation. Thanks.

[alex (r0)]

This bug emerged for me when I upgraded my system (fresh install) from 12.04 to 12.10.

I have Acer Aspire 7720G (video card is GeForce 8400M GS; nvidia-experimental-310).

uname -a
Linux notebook 3.5.0-20-generic #31-Ubuntu SMP Wed Dec 5 13:29:58 UTC 2012 i686 i686 i686 GNU/Linux

I thought that this bug is related to NetworkManager (https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1066484) as I often use bittorrent. But it appears even if I just left the computer on for a while.

I'd noticed that if I log off (via GUI) first and then shut down (GUI too) from the greeter screen it shuts down properly no matters how long the computer is on.

[no!chance (ralf-fehlau)]

I have this problem, too, but on a ubuntu SERVER system. Today I upgraded from 10.04 to 12.04 and my machine does not power off most of the times. It's frustrating. With 10.04, there were no problems. I used this machine for nightly archiving data and for nightly backups of my server, with WOL enabled and automated shuitdown. It worked perfectly a very long time, until today.

I guess, this problem has nothing to do with any desktop environment. Maybe it is kernel-related?
My system is an ASUS E35M1-I DELUXE.

[no!chance (ralf-fehlau)]

I seems, that the kernel option "acpi=force" solves my problem on the ASUS E35M1-I motherboard.

[Stefanbowe (stephan-bowe)]

Hi, I report (potentially) the same bug for two laptops
Both laptops worked fine with Lucid Lynx LTS until I upgraded them to Precise Pangolin LTS

1) Lenovo T61w:
Shutdown usually works, somtimes (about one of 5-10 times) it doesnt. When it fails, the screen turns black anyways, I can only tell by the leds or by the fan that its not properly turned off.

2. Toshipa Sattelite
Shutdown never works. The sreen freezes in the ubuntu shutdown splash animation.

acpi= force (as posted in #154) didn‘t solve it here.

[Mercer Rivière (vincentuq)]

Current LTS here. After upgrading from the previous LTS, shutdown does not work. It used to work.

[zuliani (aldo-zuliani)]

Same with my Dell Inspiron 1720 ...

The problem seems to be related to the "Nvidia propietary driver", not the Ubuntu OS.

Everything (shut down, restart) work perfectly since I have removed all the Nvidia stuff, as in : http://askubuntu.com/questions/189347/how-can-i-uninstall-nvidia-proprietary-drivers

Ctrl+Alt+F1
          - Login with your username and password
$ sudo stop lightdm
          - Press Enter
$ sudo apt-get purge nvidia*
          - Y (yes) at the question
          - Press Enter
$ sudo apt-get install xserver-xorg-video-nouveau
          - Press Enter
$ sudo reboot

Done ! The opensource driver "nouveau" works perfectly (and better than the Nvidia one), so don't worry.

[Andre (ajx)]

I cannot concure on the conclusion that it is related to closed-source drivers exclusively. I have the problem on 2 machines with Intel graphics, and not a single proprietary driver installed. They only shut down completely and switch the power off in 50% of the shutdown attempts. In general all my machines (I oversee more than the two which won't switch the power off) take ages to shutdown since Precise. I recenlty upgraded one machine to Quantal: it does shut down, but I can basically get a coffee until it finaly powers off. Up to Oneiric everything was fine: quick shutdown, and relyable poweroff.

Although this bug is declared "fixed", none of the above "fixes" have had any impact on the weird behavior at shutdown.

[Stefanbowe (stephan-bowe)]

After sleeping a night over what I‘ve read so far, I had the following idea. We might have a race condition here. In this case it would many strange things seem plausible:
 that it doesn’t happen on every shutdown
that acpi=force works on some machines
that removing the nvidia-driver works somtimes
 and so on.

Maybe someone with deeper knowledge than mine can suggest a smart spot inside the shutdown scripts to put a ‘sleep 1‘ (or similar)?

[Adolfo Jayme Barrientos (fitojb)]

Please don't mess with bug statuses.

[Nick Sharp (njsharp)]

I didn't

regards

Nick Sharp

On 07/01/13 14:49, Adolfo Jayme Barrientos wrote:
> Please don't mess with bug statuses.
>
> ** Changed in: linux (Ubuntu Precise)
> Status: Fix Released => Confirmed
>

--
Nick Sharp
eMl: <email address hidden>
Add: 77 Brighton Street
         Curl Curl
         NSW 2096
         Australia
Tel: [phone]
Mob: [phone]

[Tom Sparrow (tsparrow42-deactivatedaccount)]

Had the same "not shutting down" problem, fan continued to run.
I removed the graphics driver $ sudo apt-get purge nvidia*
Then installed the non-experimental one in "additional drivers" through the software center.
No problems since.

AMD FX(tm)-4100 Quad-Core Processor × 4
VGA compatible controller: NVIDIA Corporation GT218 [GeForce 8400 GS] (rev a2)

[Jordan H (the-jman)]

Also confirmed to happen on 12.04 Server with Supermicro X9DRW-iF motherboard. Hangs during reboot until you power cycle. CentOS works normally on these motherboards.

[razor (razorxpress)]

It affects 12.04 on dell inspiron n4110 too.

[David (damarper)]

I changed the GUI from unitiy to gnome classic (no effects) and that fixed
the problem... Has anyone had the same experience?

Laptop SAMSUNG R540
Graphics VESA M92

2013/2/1 razor <email address hidden>

> It affects 12.04 on dell inspiron n4110 too.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/987220
>
> Title:
> System does not power off reliably when "Shut Down" chosen from GUI
>
> Status in The Session Menu:
> Invalid
> Status in “gnome-session” package in Ubuntu:
> Invalid
> Status in “indicator-session” package in Ubuntu:
> Invalid
> Status in “linux” package in Ubuntu:
> Confirmed
> Status in “upstart” package in Ubuntu:
> Invalid
> Status in “gnome-session” source package in Precise:
> Invalid
> Status in “indicator-session” source package in Precise:
> Invalid
> Status in “linux” source package in Precise:
> Confirmed
> Status in “upstart” source package in Precise:
> Invalid
>
> Bug description:
> Shutting down the computer using the menue does not work always correct.
> It often does not complete turn off the computer. The power LED and the LED
> of the bluetooth unit remain on. Also the fan is still running and won't
> stop.
> Shutting down the computer with "sudo shutdown -h now" using the
> terminal works fine.
>
> I am using a Dell Inspiron 1720.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 12.04
> Package: indicator-session 0.3.96-0ubuntu1
> ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
> Uname: Linux 3.2.0-23-generic i686
> NonfreeKernelModules: nvidia
> ApportVersion: 2.0.1-0ubuntu5
> Architecture: i386
> Date: Mon Apr 23 12:26:10 2012
> ExecutablePath: /usr/lib/indicator-session/gtk-logout-helper
> InstallationMedia: Kubuntu 10.04.1 LTS "Lucid Lynx" - Release i386
> (20100816.2)
> ProcEnviron:
> SHELL=/bin/bash
> PATH=(custom, no user)
> LANG=de_DE.UTF-8
> SourcePackage: indicator-session
> UpgradeStatus: Upgraded to precise on 2012-04-21 (1 days ago)
> ---
> ApportVersion: 2.0.1-0ubuntu7
> Architecture: i386
> DistroRelease: Ubuntu 12.04
> InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386
> (20120423)
> NonfreeKernelModules: nvidia
> Package: upstart
> PackageArchitecture: all
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
> Tags: precise
> Uname: Linux 3.2.0-24-generic-pae i686
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/indicator-session/+bug/987220/+subscriptions
>

[Ken Sharp (kennybobs)]

Yes, the problem is removed when you remove Unity. The logs show a
permissions problem of some sort.

[Etai Sandow-Vandel (itay-vandel)]

I switched to KDE (Unity had not been removed, just not in use) and have
not been suffering from the issue since.

So far this seems to have affected multiple users, multiple kernels and a
broad range of hardware. The only common denominators thus far, seem to be
Unity and either the nVidia driver or fglrx.

[Stefanbowe (stephan-bowe)]

My Computers (see post above) are both running KDE (ever since). One of the Computers (Toshiba) does not have a nvidia card.

[Fabrizio Cipriani (fabriziocip)]

I've been suffering from this issue almost at every shutdown since I installed Ubuntu (first 12.04 then 12.10), it disappeared when I switched to KDE a couple of weeks ago. The more the system is used, the more likely is the issue to happen, but I was never been able to reproduce it systematically. I have an ATI Radeon HD 3600 and fglrx-legacy 8.97.100.7.

[J T (jackt-d)]

Like above (Fabrizio) - the longer i work, the bigger probability of shutdown problem. IT IS NOT A HARDWARE ISSUE, because the parallel system (zubuntu based on 10.04) always shuts down correctly.

[Stefanbowe (stephan-bowe)]

I agree that it the cause does not seem to be a hardware issue. However, the result is a hardware issue in my case: Every time that I don’t realize that my laptop doesn‘t turn off, my battery runs empty. This decreases its capacity and lifetime.

[Skilly (michael-scheepers)]

Same problem as described in this thread.

My hardware is Dell XPS12

[Stefanbowe (stephan-bowe)]

Hi, on one laptop (Lenovo T61w) switching to the nouveau-driver helped! All shutdowns completed successfully since then. The other laptop (Toshiba sattelite) has no NVIDIA-Card, so I am looking for another solution for it.

[anders (anderspn)]

My Labtop still hangs If i do a shutdown from unity. However I have found a workaround which is to chose logout and then select shutdown from the login screen. This works every time.

Seems like something breaks after running unity for some time, but it gets reset when the X server is restarted by doing a logout.

[Orosz Gyozo (oroszgyozo)]

"Solved" the problem by removing the NVIDIA drivers and using nouveau instead .... :(
( Xubuntu 12.04 )

[Patrick den Ouden (inf5)]

Same problem on Mint 14 KDE (based on ubuntu 12.04),
Using a HP 550 laptop.
Shutdown results in end logo showing... indefenitly.

I am not using nvidia drivers btw, i got one of the crappy intel chipsets.

However, on my main system i dont have a problem with any ubuntu build.
I'm suspecting some sort of incompatability.

[Patrick den Ouden (inf5)]

Just noticed something... the wireless drivers.
My problems start after installing both the linux-nonfree-firmware and the b34 drivers.

Any of you that have the same?

[Patrick den Ouden (inf5)]

wireless card is the infamous broadcom chip.
dunno the type from top of my head... but forums are full of "how to get it working"

[Mercer Rivière (vincentuq)]

Dell Inspiron 1520 and Ubuntu 12.04. Upgraded from previous LTS where it worked.
Shutdown isn't working. Nvidia here, I will not remove it as I don't believe there is a relationship - it may only be a workaround.
I intend to stay on this LTS. I refuse to change any BIOS settings as it worked previously.

Other, perhaps unrelated:
- Sometimes X11 have 100% CPU and everything freezes
- ctrl-alt-f1 does not show a text terminal
- often kernel oopses, more info here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1154006

[wantlamy (wantlamy)]

I have the same problem with Debian wheezy(gnome 3), this is why I come to ubuntu 12.04. Unfortunately ubuntu has the problem too. But Debian wheezy with xfce desktop environment can shutting down normally with a warn message sometimes: killing all remaining processes failed.

[Wolter HV (wolterh)]

Am I the only one who gets an error saying that I should stop S15networking via sudo service networking stop or sudo stop networking?

I tried running that command alone and I get a crash. Perhaps this is what's causing the problem?

[Koen Roggemans (koen-roggemans)]

I have it with several Intel Classmate with an Atom N2600 chipset

[penalvch (penalvch)]

Mark Schneider, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc6

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[plum7500 (plum01)]

Most of the time when I set SABnzbd to shutdown computer after it finishes downloading files, it will work.
I've had this issue since doing a fresh install of 12.04.

[penalvch (penalvch)]

plum7500, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Mercer Rivière (vincentuq)]

Works in 3.2.0-51-generic (Inspiron 1520).

[gratefulfrog (gratefulfrog)]

This afffects me on 12.04 running on an Asus EEEpc 1201n.... It is systematic, the computer never completely powers off anymore, altough it used to some time ago.

Also, I run Gnome not Unity.

Cheers,
Bob

[penalvch (penalvch)]

gratefulfrog, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[nafur (nafur)]

Had the same problem (System powered off, but hardware did not actually turn off) on a dell vostro V131.
Problem persisted on installed Ubuntu and Windows 7 as well as Ubuntu and Fedora live systems (from USB)
As suggested in this thread: http://en.community.dell.com/support-forums/laptop/f/3518/t/19450900.aspx?pi239031352=1
I removed the BIOS battery for a few minutes. This solved the problem for me.

[netikras (netikras)]

Affects Linux Mint Petra as well. I'm on Samsung NF-210.

Issuing 'init 6' seems to kill processes and hung at blank screen. This actually has started quite a while ago.. >1 year ago. Then I used to notice this problem when hibernating with 's2disk' or 's2both' after using computer for a while (never occurred on a fresh boot). It used to fail to poweroff (although succeeded to dump the image) then too, but I decided it's simply because there are too many applications open and there's simply not enough of swap memory to store the image, or something like that... However a few weeks ago 'init 6' started to fail as well as simple shutdown...

Dunno if this could be related, but samsung-tools started to fail in re-enable wifi after waking up the OS from SLEEP (s2ram).

[netikras (netikras)]

umm.... just forgot to mention.. When it turned into zombie (almost dead) after attempt to hibernate I had to poweroff it manually with the button. After powering it on again fresh OS used to boot instead of the hibernated image (although uswsusp claimed image is saved at 100%). So I believe it's OS preventing computer from powering-off...

[penalvch (penalvch)]

nafur / netikras, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu (not Linux Mint) by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[George (geoaraujo)]

It seems that I'm plagued by this issue too.
Dell Inspiron N 4050 and Kubuntu 14.10. Upgraded from previous LTS where it worked.
Intel Integrated Graphics card here.

[penalvch (penalvch)]

George, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Gregory Kramida (algomorph)]

Judging by the number of different architectures affected, I speculate that bug occurs on a specific class of hardware (specific set of motherboard chipsets?)

I have had this same (or similar?) issue plaguing two of my desktop machines out of three. All have Ubuntu 15.04 currently on all three, all three have similar hardware configurations and the same M/B vendor, yet different motherboards.

What I would like to know is, specifically with what hardware components could shutting down become an issue? How would I find out which one I have (maybe, specific entries in output of "lspci", something in the kernel log, etc.)? How do I determine whether two of my machines are suffering from this same bug or a different one?

-Thanks

[Rile (rile-tm86)]

I have this problem after replacing my HDD with new SDD. Since than, everything is much faster but it wont't power off.

This is a thread about my issue: http://ubuntuforums.org/showthread.php?t=2292569

[jose castellanos (joscastel2014)]

I installed, from pendrive, Ubuntu 16.04 LTS in dell inspiron 1501 (with windows XP), the windows poweroff normally, but ubuntu do not: it goes shutdown apparently normally but finally do not power off the labtop.

The last lines reported are: All fylesystems unmounted Deactivating swaps All swaps deactivated Detaching loop devices All loop devices detached Detachig DM devices All DM devices detached Powering off

and the labtop do not power off

Ther is a significant note in the previous lines before those lines: Process 1043 (plymouthd) has benn marked to be ecluded form killing.......

I am new and no expert linux

[penalvch (penalvch)]

jose castellanos, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[Steve Langasek (vorlon)]

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release