Suspends to RAM when shutdown order has been given if laptop lid is closed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
When I click to shutdown the laptop, if I close the lid before the shutdown process is completed, the laptop goes to sleep. This is annoying because it is consuming battery but specially because the suspend to RAM does not cancel the shutdown. When I open the laptop again, it restores from RAM, takes several minutes to shutdown and then I have to turn it on again.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.21
ProcVersionSign
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: KDE
Date: Thu May 16 16:26:41 2019
InstallationDate: Installed on 2019-02-23 (82 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 5986:111c Acer, Inc
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20K5S0T200
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: systemd
SystemdDelta:
[MASKED] /etc/systemd/
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
3 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/02/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0IET36W (1.14 )
dmi.board.
dmi.board.name: 20K5S0T200
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad X270 W10DG
dmi.product.name: 20K5S0T200
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
Changed in systemd (Ubuntu): | |
importance: | Undecided → Medium |
Oh joy! This is like the ultimate "have you tried turning it on and off again".
I wonder, if shutdown should inhibit sleep as its first action. And/or sleep api should be checking for in flight shutdown transaction.
I agree this is a bad behaviour.