unable to shutdown

[Harkishan Singh]

stops at "will halt" or sumthin

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-46-generic 3.13.0-46.76
ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kishan 2048 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Mar 4 09:47:18 2015
HibernationDevice: RESUME=UUID=f58ae439-bd92-4bb4-adeb-d8c564d12e39
InstallationDate: Installed on 2015-02-26 (5 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 002 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd
 Bus 002 Device 002: ID 04ca:300b Lite-On Technology Corp.
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire ES1-311
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=c3d4952b-a5c3-489c-99f1-7331a352b71f ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-46-generic N/A
 linux-backports-modules-3.13.0-46-generic N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Aspire ES1-311
dmi.board.vendor: Acer
dmi.board.version: V1.07
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.07
dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.07:bd08/13/2014:svnAcer:pnAspireES1-311:pvrV1.07:rvnAcer:rnAspireES1-311:rvrV1.07:cvnAcer:ct10:cvrV1.07:
dmi.product.name: Aspire ES1-311
dmi.product.version: V1.07
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/

[Harkishan Singh (kishan9778)]

in kernel 4.0,same as kernel 3.16 and 3.18,the touchpad wont work.

in kernel 3.16,the shutdown problem is solved,but the touchpad is not recognized

in 3.18 and 4.0,touchpad and shutdown problems prevail

[Harkishan Singh (kishan9778)]

I updated the BIOS after installing Win8 x64 succesfully,then I reinstalled Ubuntu 14.04.1,I am happy to report that the shutdown prolem is finally solved,thanks a bunch :)

although the BIOS update succesfully solved the situation,I will still post the outcome of dmidecode -s bios version and dmidecode -s bios-release-date

V1.10
10/24/2014

[Harkishan Singh (kishan9778)]

update

the problem came back...very dissapointing

[penalvch (penalvch)]

Harkishan Singh, could you please test the latest mainline kernel (4.0-rc3) and advise to the results?

[Harkishan Singh (kishan9778)]

Well 4.0 rc3 worked splendidly and being a stable-kernel-generic guy,i installed 14.10 (with kernel 3.16.0-31-generic) and the problem is now solved,alongwith a host of other problems such as brightness,bluetooth and battery

[penalvch (penalvch)]

Harkishan Singh, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1427947/comments/11 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Martin (axiomize)]

It's a bit strange because I have a rather similar setup (see bug #1449252) but none of the kernels 3.16, 4.0 and 4.1rc1 solved the problem.

[penalvch (penalvch)]

Martin, this bug report is closed, and wasn't scoped to your hardware. If you want your issue addressed, please file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.