Shutdown restarts the computer
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Whenever I shutdown Ubuntu, my computer reboots instead of shutting down. This happens either shutting down:
- from the shut down menu
- pressing the power button and selecting Shut Down in the dialog
- issuing sudo shutdown -h NOW
Running a uname -a gives:
andy@argherna-01:~$ uname -a
Linux argherna-01 2.6.35-27-generic #48-Ubuntu SMP Tue Feb 22 20:25:29 UTC 2011 i686 GNU/Linux
andy@argherna-01:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
My hardware is a Gateway 450 ROG (old laptop). I freshly installed 10.10 due to a failed upgrade from 9.10 to 10.04. Thanks for your help.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-27-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'I82801DBICH4'
Mixer name : 'SigmaTel STAC9752,53'
Components : 'AC97a:83847652'
Controls : 38
Simple ctrls : 24
Date: Tue Mar 15 21:05:15 2011
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
Lsusb:
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
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gateway Gateway 450ROG
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
RelatedPackageV
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
dmi.bios.date: 04/03/2003
dmi.bios.vendor: Gateway
dmi.bios.version: 40.01.04
dmi.board.name: Gateway 450ROG
dmi.board.vendor: Gateway
dmi.board.version: Rev 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.
dmi.modalias: dmi:bvnGateway:
dmi.product.name: Gateway 450ROG
dmi.product.
dmi.sys.vendor: Gateway
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Andy Gherna, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ .
If it remains an issue, 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? It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.
If this bug is fixed in the mainline kernel, please add the following tag 'kernel- fixed-upstream' .
If the mainline kernel does not fix this bug, please add the tag: 'kernel- bug-exists- upstream' .
If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel- unable- to-test- upstream' , and comment as to why specifically you were unable to test it.
Please let us know your results. Thanks in advance.
Helpful Bug Reporting Links: /help.ubuntu. com/community/ ReportingBugs# Bug_Reporting_ Etiquette /help.ubuntu. com/community/ ReportingBugs# A3._Make_ sure_the_ bug_hasn. 27t_already_ been_reported /help.ubuntu. com/community/ ReportingBugs# Adding_ Apport_ Debug_Informati on_to_an_ Existing_ Launchpad_ Bug /help.ubuntu. com/community/ ReportingBugs# Adding_ Additional_ Attachments_ to_an_Existing_ Launchpad_ Bug
https:/
https:/
https:/
https:/