Live session hangs at poweroff or reboot

Bug #1562391 reported by Paul White
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

Both 32 and 64-bit versions of Lubuntu daily ISO do not poweoff or reboot when requested so Power button must be used to terminate session.

This may be similar to bug #1552985 but a new bug reported at the request of Christopher Penalver.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-15-generic 4.4.0-15.31
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic i686
ApportVersion: 2.20-0ubuntu3
Architecture: i386
 /dev/snd/controlC0: lubuntu 1614 F.... lxpanel
CasperVersion: 1.369
CurrentDesktop: LXDE
Date: Sat Mar 26 20:25:28 2016
LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta i386 (20160326)
 PATH=(custom, no user)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=gb
 linux-restricted-modules-4.4.0-15-generic N/A
 linux-backports-modules-4.4.0-15-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install) 07/25/2014
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 1.40
dmi.board.asset.tag: * ZBWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd07/25/2014:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCMLE-04901DEN:rvnTOSHIBA:rnZBWAA:rvr1.00:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: SATELLITE C50-B
dmi.product.version: PSCMLE-04901DEN
dmi.sys.vendor: TOSHIBA

Revision history for this message
Paul White (paulw2u) wrote :
Revision history for this message
penalvch (penalvch) wrote :

Paul White, thank you for reporting this and helping make Ubuntu better.

As per an update to your computer's buggy, insecure, and outdated BIOS is available (5.10). If you update to this following does it change anything?

For more on BIOS updates and linux, please see .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your understanding.

tags: added: bios-outdated-5.10
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Revision history for this message
Paul White (paulw2u) wrote :

Unable to update BIOS at this time.
Retested with both 32 and 64-bit ISOs with newer USB drive and both power off or reboot correctly.
Older USB drive never failed before so had no reason to doubt it. Sorry for any inconvenience.
Marking bug as "Invalid"

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
sudodus (nio-wiklund) wrote :

I have seen indications that it makes a difference which tool or method was used to create the USB boot drive. So please tell us which tool was used when this bug appeared, as if you get different results when trying to shut down, when the USB drive was created with different tools or methods.

Revision history for this message
Paul White (paulw2u) wrote :

sudodus, all tests were made using Startup Disk Creator (in Xubuntu 16.04) to create the boot drive.

Revision history for this message
sudodus (nio-wiklund) wrote :

It seems to me that this bug affects systems booted via syslinux, but not systems booted via grub.

See this comment to a related bug report,

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.