If I use "shutdown" from the gui or invoke it from the command line (with power down and halt options) it doesn't power off the machine.

[laptoplinux]

They both shutdown the OS but then the machine power is left on and I must turn it off from the power button.

p:~$ uname -a
Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

:~$ sudo dmidecode -s system-manufacturer
TOSHIBA
:~$ sudo dmidecode -s system-product-name
dynabook TX/760LS
:~$ sudo dmidecode -s system-version
PATX760LS

[Parthan SR (parth-technofreak)]

Thanks for taking the time to report this bug. Unfortunately we can't look into your bug because your description doesn't yet have enough information we require.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:

1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies. Thanks in advance!

[Parthan SR (parth-technofreak)]

Am in doubt, is this anyway related to bug #121902 and can be marked a duplicate of it? Thanks.

[laptoplinux (laptoplinux)]

:~$ uname -a
Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux

[laptoplinux (laptoplinux)]

Parthan,

Did the requested information shed any light on this problem? I haven't received any feedback.

Are you indicating that this should be marked as a duplicate? My bug is in Hardy and bug you referenced was in Feisty. I thought because of that it warranted a separate thread.

[Parthan SR (parth-technofreak)]

Thanks for giving us the required information. I was not sure whether both are similar kind of bugs or rather both are same problem or not, hence I mentioned the other bug as well.

[Parthan SR (parth-technofreak)]

As the information sought was provided by the bug reporter, am changing the status back to New from Incomplete.

[Parthan SR (parth-technofreak)]

Confirming this bug as required information have been provided by the reporter. Not sure of being a duplicate of bug #121902 as that bug is still not confirmed to any more exist. Thank you.

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Pablo Castellano (pablocastellano)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Hagen (hagenf)]

I'm having a similar problem with Jaunty: Occasionally after shutdown my laptop won't power off. Please tell me if I can help in resolving this by providing more information or trying a different kernel version!

[Waluyo Adi Siswanto (was-wlk)]

I have a similar problem in Jaunty and reported here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/377897

in this kernel version
Linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

[kernel-janitor (kernel-janitor)]

Hi laptoplinux,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . Please then run following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 257507

Also, if you could 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.]

[laptoplinux (laptoplinux)]

Architecture: i386
DistroRelease: Ubuntu 9.04
HibernationDevice: RESUME=UUID=e152dfb2-6c5f-4825-aac7-6e1647659c19
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: TOSHIBA dynabook TX/760LS
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
PackageArchitecture: i386
ProcCmdLine: root=UUID=de35718e-4c10-47b7-9084-40b49d14dab7 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

[laptoplinux (laptoplinux)]

This is no longer an issue for me after aptitude safe-upgrade downloaded the latest kernel update today.