lucid doesn't shut down completely

[Dr. Kenobi]

Binary package hint: plymouth

1)
joaquin@joaquin-laptop:~$ lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04
joaquin@joaquin-laptop:~$
2)
joaquin@joaquin-laptop:~$ apt-cache policy plymouth
plymouth:
  Installed: 0.8.2-2ubuntu2
  Candidate: 0.8.2-2ubuntu2
  Version table:
 *** 0.8.2-2ubuntu2 0
        500 http://ar.archive.ubuntu.com/ubuntu/ lucid/main Packages
        100 /var/lib/dpkg/status
joaquin@joaquin-laptop:~$
3) I expected the computer to shut down
4) The computer never shuts down if I close the lid of the laptop right after pressing "Shut Down" at the popup window.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: libplymouth2 0.8.2-2ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Thu May 6 00:38:57 2010
DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems)
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 002: ID 13fe:1f00 Kingston Technology Company Inc. DataTraveler 2.0 4GB Flash Drive / Patriot Xporter 32GB (PEF32GUSB) Flash Drive
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Compaq Evo N610c
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   3.3V 32-bit PC Card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=49c35f9d-8ea7-458d-a23d-8f3a07d1d9d1 ro quiet splash
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
dmi.bios.date: 04/01/2004
dmi.bios.vendor: Compaq
dmi.bios.version: 68P4F Ver. F.1A
dmi.board.name: 07F4
dmi.board.vendor: Compaq
dmi.board.version: KBC Version .
dmi.chassis.asset.tag: 1J2AKT8ZM305
dmi.chassis.type: 10
dmi.chassis.vendor: Compaq
dmi.modalias: dmi:bvnCompaq:bvr68P4FVer.F.1A:bd04/01/2004:svnCompaq:pnEvoN610c:pvr:rvnCompaq:rn07F4:rvrKBCVersion.:cvnCompaq:ct10:cvr:
dmi.product.name: Evo N610c
dmi.sys.vendor: Compaq

[Boudhayan Gupta (baloneygeek)]

This one affects me as well.

My video hardware is an ATI Radeon HD4330 (Mobility), on a Dell Vostro 1088n.

What happens after shutting down is:
1) If I use the Shut Down option in GNOME, after all the services have halted, my computer freezes and I have to press the power button for 5 seconds to shut the thing down.
2) If I use the Restart option, after all the services have halted, I just have to normally press the power button like I do when starting the thing, to shut it down.

Removing Plymouth fixes the problem.

This problem also occurs in Arch Linux, after installing Plymouth

And manually compiling and installing kernel 2.6.34-rc4 had fixed it for me, but I went back to using the official kernel.

[David Llop (dllop)]

Hi colleagues.

After upgrade to 10.04 from 9.10 my computer doesn't shut down. You can select and accept the option under GNOME but it doesn't shut down.

lsb_release -rd
Description: Ubuntu 10.04 LTS
Release: 10.04

Greetings

[Steve Langasek (vorlon)]

If you press 'esc' at the shutdown plymouth screen, what does the console show?

This is unlikely to be a bug in plymouth, as plymouth itself is not in a position to stop the shutdown. This may be a kernel bug.

[Boudhayan Gupta (baloneygeek)]

Dear Steve,

The computer completely locks up. So nothing happens if I press ESC. By the way, on Arch using Kernel 2.6.33, this problem wasn't there before I installed Plymouth. It did come after I installed Plymouth. Also, if I use a kernel from Ubuntu's Upstream Kernels repo (version 2.6.43-rcX and above, where X is anything) or use a self-compiled 2.6.34-rc4, the problem goes away, but my sound stops working. And heck, even the Ubuntu Alternate CD boots up and shuts down fine. It doesn't have Plymouth, as far as I see. So the bug might be due a combination of factors involving the currently used kernel and Plymouth.

Yours,
Boudhayan Gupta

[Steve Langasek (vorlon)]

Ok, what happens if you press Alt+SysRq+K at the shutdown screen?

[Steve Langasek (vorlon)]

Also, I need answers to these questions from the original bug submitter.

[Dr. Kenobi (drkenobi)]

Hi, here is the original submitter! :o)

When I press ESC the screen turns black with some white letters, and if I press ESC again it goes back to the original screen.

The black screen says:

Broadcast message from root@joaquin-laptop
             (unknow) at 6:15 ...

The system is going down for halt NOW!
acpid exciting
init: avahi-daemon main process (725) termnated with status 225
init: tty4 main process (888) kill by term signal
init: tty5 main process (893) kill by term signal
init: tty2 main process (900) kill by term signal
init: tty3 main process (901) kill by term signal
init: tty6 main process (903) kill by term signal
init: cron main process (909) kill by term signal
init: tty1 main process (1067) kill by term signal
[ 2943.836257] end_request: I/O error, dev fdo, sector 0
Init: network-manager main process (745) killed by KILL signal
modem-manager: Caught signal is, shutting don...
Init: Disconnected from system bus

I tried 'CTRL+ALT+F1', 'CTRL+ALT+F2', 'CTRL+ALT+F3', 'CTRL+ALT+F4', 'CTRL+ALT+F5', 'CTRL+ALT+F6' and nothing worked. This was at 10:30, so the laptop stayed on for 4 hours.

It doesn't happened always. I think its every time I shut down my laptop and close the lid before it is completely off.

[RobertH (rh-roberthale)]

Hi,
I am the submitter of duplicate bug 579999.
This issue has been "fixed" for me by doing the following:

sudo gedit /etc/default/grub

change : GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to : GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi=force"

sudo update-grub

[Steve Langasek (vorlon)]

On Fri, May 14, 2010 at 01:52:01PM -0000, Dr. Kenobi wrote:
> I tried 'CTRL+ALT+F1', 'CTRL+ALT+F2', 'CTRL+ALT+F3', 'CTRL+ALT+F4',
> 'CTRL+ALT+F5', 'CTRL+ALT+F6' and nothing worked. This was at 10:30, so
> the laptop stayed on for 4 hours.

Please boot without 'quiet' on the kernel command line and repeat this test
(but be sure to still include 'splash' on the commandline).

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[frenchy82 (cartes)]

I've uninstalled plymouth from my lubuntu 10.04 and for the first time i could shutdown properly my computer.
I've tried a lot of option from boot and only uninstalling plymouth help on lucid
(i imagine, i will must wait for more time to confirm this)

kernel : 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux

[Steve Langasek (vorlon)]

> I've uninstalled plymouth from my lubuntu 10.04 and for the first time i could
> shutdown properly my computer.
> I've tried a lot of option from boot and only uninstalling plymouth help on
> lucid

This is false. Uninstalling the plymouth package would render your system unbootable, so whatever you did, you didn't uninstall plymouth.

[Dr. Kenobi (drkenobi)]

Steve, I've no idea how to do it. Can u please explain to me?

I've been thinking for a while, and if u r asking me to do something before the system starts to boot, by pressing ESC, I can't do it, something is wrong. If this is not what u want, explain me and I'll do it.

Oh! I checked again and the laptop doesn't shut down only when I close the lid while it is shutting down. If I don't close the lid and wait, the laptop shuts down properly.

[frenchy82 (cartes)]

Steve Langasek : i'm sorry but this not false, From several days i'm looking what is wrong with my computer.

I was really afraid to damage my computer

So i tried to use mountall from https://launchpad.net/~dtl131/+archive/mediahacks/+packages, and with this you can uninstall plymouth just to verify if it could help where the problem come from

And since yesterday i can shutdown my computer
But maybe, it's a coincidence

[Alfonso Díaz (alfonsodf)]

<i>

Hi,
I am the submitter of duplicate bug 579999.
This issue has been "fixed" for me by doing the following:

sudo gedit /etc/default/grub

change : GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to : GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi=force"

sudo update-grub
</i>

Works for me

[Steve Langasek (vorlon)]

On Sun, May 16, 2010 at 04:42:46AM -0000, frenchy82 wrote:
> So i tried to use mountall from
> https://launchpad.net/~dtl131/+archive/mediahacks/+packages, and with
> this you can uninstall plymouth just to verify if it could help where
> the problem come from

Ah; this is a key detail you omitted from your earlier message.

Yes, if you're not using the official mountall package, it may be possible
to remove plymouth. But that makes your system so different from 10.04 that
it doesn't help much to pinpoint the source of the problem.

Anyway, if you are *never* able to shut down cleanly while plymouth is
installed, I think you should file a separate bug report.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[rictec (rictec-netcabo)]

hi
my system 10.04 uograded from 9.10 doesnt have that file

sudo gedit /etc/default/grub

empty file
maybe thats the problem?..

rictec

[Steve Langasek (vorlon)]

On Sun, May 16, 2010 at 11:28:43PM -0000, rictec wrote:
> hi
> my system 10.04 upgraded from 9.10 doesnt have that file

> sudo gedit /etc/default/grub

> empty file
> maybe thats the problem?..

That just indicates that you have grub 1 installed rather than grub 2;
that's not a bug, it just means you would need to make your changes in
/boot/grub/menu.lst instead of in /etc/default/grub.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>

[zika (4zika4)]

I'm having this "problem" for quite some time, as it is documented on ubuntuforums.prg. Yes, it persists with or without Plymouth, with acpi=force etc. I've not seen the light in the tunnel yet... :) Other than power switch... :)

[rictec (rictec-netcabo)]

you are right Steve
i just assumed i did the some on the laptop as i did on the desktop pc that's was not true
i m still running grub1 on the laptop

still i just quickly press esc as soon as i shutdown and the laptop power goes down..
if ubuntu letters stays with those dots them it won t power down.

i will try acpi=force on it later

rictec

[Steve Langasek (vorlon)]

Dr. Kenobi,

To change the kernel options at boot time, power up your system and hold down the 'Shift' key while booting. This should bring up a grub menu, where you can press 'e' to edit the current boot options, then press Ctrl+X when finished to boot.

You will probably also want to test booting with acpi=force as an option, as described in comment #15.

[phpmonkey (phpmonkey)]

Using Alfonso's "quiet acpi=force" (#15) method worked for me :)

[JZ (zimmerju)]

Using "quiet acpi=force" has not resolved the problem for me. Instead of hanging at the splash screen during shutdown, it now hangs during shutdown when it says "halting system" (I think that is correct). This happens 70% of the time I shut down.

[Roland S. (kaiser-ger)]

same here. changes in /etc/default/grub to "quiet acpi=force" are without effect.

I am using Lucid desktop amd64. Hardware: MSI 785GM-E51, Phenom II, 4 GiB DDR3

[Dallman Ross (spamless)]

I'm having similar troubles on my old laptop with an Athlon chip. Pressing Esc shows a screen full of messages about broken pipes, fake processes, etc.

[Dr. Kenobi (drkenobi)]

Steve Langasek, I've changed the kernel options at boot time as you said (boot without 'quiet') but I still have the problem.

But I only have this problem when I close the lid of my laptop while the OS is shutting down. At the Power Manager Preferences I have choose to 'Suspend when the laptop lid is closed'. Maybe this is making the problem. Because if I don't close the lid while the OS is shutting down, I have no problem.

[Steve Langasek (vorlon)]

Yes, it's expected that you would still have the problem when booting without 'quiet' - but were there any new messages displayed on the screen? And did you try booting with acpi=force?

[Benoit (benoit-lachambre)]

Hi,
I have that problem with three others and, maybe, I just find a solution.
My problem were random, but a clean install don't solve the problem, because it came back in few days...

When the problem arrived, it was always the full 4 bugs.
1. Can't mount NTFS partition
2. Can't change cpu freq event with frequtils
3. The computer can't shut down...
4. Can't change the permission of my login user

Tonight, after Googling a lot, I've find a post with the permission hint. I reboot 4 times and, when everything seems to work fine, I set my permission to Administrator and reboot a new.

Since that, I've reboot two other time and it seem ok...

Maybe it's only luck...

Thanks for your efforts...

[Gordon Burgess-Parker (gordonbp)]

Robert H wrote:
"

Hi,
I am the submitter of duplicate bug 579999.
This issue has been "fixed" for me by doing the following:

sudo gedit /etc/default/grub

change : GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to : GRUB_CMDLINE_LINUX_DEFAULT="quiet acpi=force"

sudo update-grub"

This worked for me.

[Boudhayan Gupta (baloneygeek)]

Update:

It seems that the bug is KMS related, not Plymouth. After testing with other distros as well, it turns out that upto Kernel 2.6.33 has this issue, but on 2.6.34, which is used by Fedora, this issue occurs in Fedora only. Distros such as openSUSE and others, including using a self-compiled 2.6.34 in Ubuntu do not have this issue.

Was "fixed" for me by installing the proprietary FGLRX drivers. Don't know whether the issue was in the "radeon" driver, or in the KMS code as installing FGLRX disabled KMS and now everything is working fine with the default Lucid kernel.

[Gordon Burgess-Parker (gordonbp)]

Unfortunately Robert's Fix only worked once. Now nothing on the "Shutdown" menu works at all.

[Gordon Burgess-Parker (gordonbp)]

There's definitely a bug in the updated kernel.
If I boot up in the 32-21 kernel that shipped with the original install, the shutdown options work exactly as they should. If I boot into the 32-23 kernel, then they don't work at all.

[Steve Langasek (vorlon)]

There's a preponderance of evidence here that this is a kernel bug, not a plymouth bug. Reassigning.

[Boudhayan Gupta (baloneygeek)]

I am not a programmer, but something tells me the fix was done in the KMS code somewhere in between Kernel 2.6.33 and 2.6.34-rc4, which was the earliest release that worked with me. Is this issue only limited to ATI Radeon users? It may also be a libdrm or even an X issue (AFAIK KMS depends on X drivers, isn't it?)

[Jeremy Foshee (jeremyfoshee)]

Hi Dr.,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Roland S. (kaiser-ger)]

Interesting. A BIOS update did it. My MSI 785GM-E51 shuts down again, as it should.

[Dr. Kenobi (drkenobi)]

Hi! I'm not having this issue anymore. An update might have solved the bug. I'm changing the status to 'invalid'. If someone thinks the bug should be open, do it. Thank you for your time!

[phpmonkey (phpmonkey)]

I just did a clean install of maverick on my twinhead twinmate e10 and had the same issue as I did with Lucid.

Once again, using Alfonso's "quiet acpi=force" (#15) method worked for me.

Should this be reopened?

Cheers,
Jenny

[Adam Hirsch (z-launchpad-quakerporn-com)]

I can report that setting "acpi=force" does not solve the shutdown/reboot problem for me, running Lucid on an aging (but still good!) amd64. The last LTS, 8.04, was able to correctly handle this same hardware.

During the shutdown process, I can hit ESC to see the messages go by. The very last line says "Killed," and there it stops, power supply still running. The only way to reboot it is to hit the reset switch or power button.

uname -a:
Linux mwamizi 2.6.32-27-generic #49-Ubuntu SMP Thu Dec 2 00:51:09 UTC 2010 x86_64 GNU/Linux

[frenchy82 (cartes)]

I think that plymouth is the problem with my computer
I have an integrated intel chipset i815 who needs the "DefaultDepth 16" parameter in xorg.conf to work properly

With this paramter y need to deactivate plymouth if i want to shutdown my computer

If i use DefaultDepth 24, i can shutdown computer even if plymouth is activate

[Frazzle (razzledazzler2)]

I have trialled the Lucid and Maverick versions (10.x) off the CD and get this shutting down problem. Although it seems to hang at the bottom-left cursor, it's NOT SO as I can type 'exit' and the shut down continues. But I can still do without this and now I'm reading about this problem with the installed program. I hope that this gets fixed soon and announced as so as this can dent confidence in the product: we're fleeing Windows 'cos we don't want silly problems like I/O errors when the hardware is fine! I've never had this problem with version 8.04 (Hardy) and if anyone can point me to a version later than that before 9.0, or Hardy Server then I'd be grateful. Thank you.

[Gotit (sca957)]

I have tried the "acpi=force" fix but it did not work for me.

I just built a new system with:
 AMD Phenom X4
 MSI mobo 880GM-E43
   -ATI Radeon HD4250 GPU onboard (more on this below)
 MSI nvidia GeForce 9400 GT
 Ubuntu 10.04.2 kernel 2.6.32-30-generic-pae

I installed 10.04.2 and had the no shutdown problem. So I tried to load the ATI driver using System > Administration > Hardware Drivers to see if that would help.
Driver install failed the first time tried with a non-specific error. I tried again and the driver installed successfully. On re-boot the display was bad (see attached) so I went back to the stock Ubuntu driver. However, I did not get a boot splash screen. So I installed the MSI nvidia GeForce 9400 GT card I had and loaded he nvidia driver using System > Administration > Hardware Drivers. Splash screen now seen. Still had the no shutdown problem. So, doesn't seem to be video driver related as I had the problem with both stock and proprietary drivers.

Checked MSI for updated BIOS but I am very current with only 1 new rev available. It seems to be a very minor bug fix and would have nothing to do with my shutdown problem.

If I press Esc after selecting shutdown I see the text of what is happing during the shutdown process. The text seems normal and even gives a "shutdown" command at the end and then just hangs there. I must press the power button to shutdown the system.

Attached: uname -a, lspci and display screen shot with ATI driver.

[Gotit (sca957)]

As a follow up, if I boot from a 10.04 live cd and try to shut down my system gets to the point of saying "remove the cd and press enter". However, the system will not shut down it just hangs there.

When I boot with 9.10 live cd and shut down it works as expected. After I remove the cd and press enter the machine shuts down normally.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Gotit (sca957)]

and so goes our hope for a fix...

[iBART (mogio)]

so do I, cannot shutdown: system stops, machines hangs on "halting system..." :(