Cannot configure suspend-then-hibernate

Bug #1947708 reported by Larry Skywalker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Previous bug 1947617 was closed because my swap space was insufficient. Swap was increased to 24G and the problem remains.

Configuring login to suspend-then-hiberrnate when the lid is off and configuring sleep so that hibernate happens 10 seconds after suspend, when trying to test with:

sudo systemctl suspend-then-hibernate

I get:

Failed to suspend system, hibernate later via logind: Sleep verb "suspend-then-hibernate" not supported

This could be a security vulnerability. If the user expects the system to suspend (and then lock) when the lid is off and it does not work, somebody could then just reopen the lid and get access.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: systemd 248.3-1ubuntu8
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: i3
Date: Tue Oct 19 11:51:50 2021
InstallationDate: Installed on 2021-10-14 (4 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: HP HP ENVY x360 Convertible 13-ay0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=e85d08c2-ae82-4f0f-a625-a5012616c934 ro quiet splash vt.handoff=7
SourcePackage: systemd
SystemdDelta:
 [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED] /usr/lib/systemd/system/systemd-localed.service → /usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
 [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf

 3 overridden configuration files found.
SystemdFailedUnits:
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
 ------
 Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?).
 Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/30/2021
dmi.bios.release: 15.20
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 876E
dmi.board.vendor: HP
dmi.board.version: 12.52
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 12.52
dmi.modalias: dmi:bvnInsyde:bvrF.20:bd07/30/2021:br15.20:efr12.52:svnHP:pnHPENVYx360Convertible13-ay0xxx:pvrType1ProductConfigId:sku3V693EA#ABF:rvnHP:rn876E:rvr12.52:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 13-ay0xxx
dmi.product.sku: 3V693EA#ABF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
mtime.conffile..etc.systemd.logind.conf: 2021-10-18T18:51:43.976989
mtime.conffile..etc.systemd.sleep.conf: 2021-10-18T18:52:04.283409

Revision history for this message
Larry Skywalker (larryskywalker) wrote :
Revision history for this message
Dan Streetman (ddstreet) wrote :

> [ 82.230208] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7

you're using UEFI secure boot, which puts the system into 'lockdown', which disallows (unencrypted) hibernation.

So this isn't a problem with systemd, this requires the kernel to handle encrypted hibernation.

I *think* that functionality isn't yet in the upstream kernel, as I think this thread was the last discussion about adding it:
https://<email address hidden>/

affects: systemd (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Larry Skywalker (larryskywalker) wrote :

Indeed, disabling secure boot fixes the problem.
As far as I am concerned, this workaround is find with me.

Thanks for your help Dan.

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.