suspend does not lock in 18.04

Bug #1798615 reported by John Crown on 2018-10-18
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

To reproduce from the command-line (this is ubuntu 18.04):

% gsettings set org.gnome.desktop.screensaver ubuntu-lock-on-suspend true
% gsettings get org.gnome.desktop.screensaver ubuntu-lock-on-suspend

% systemctl suspend

Now the monitors go black and report "no signal" (good), and it will stay that way for hours (good) ... but if I tap "shift" key a few times, Ubuntu 18.04 comes back without asking my password. (I expected rather that the system would be locked, i.e. I should see a dialog box that would require a password before anything else!)

Same thing if I suspend by using the upper-right-of-screen "power" icon (click-and-hold, then click on the suspend icon).
Same thing if I let 20 minutes go by. (A msg comes up ~~ "system will suspend soon...", and it does suspend, but doesn't lock).

I have left the ubuntu-lock-on-suspend setting at "true" through several re-boots, but it still doesn't take effect.

I get the same behavior whether ubuntu-lock-on-suspend is set to "true" or "false".

Other info:
% wmctrl -m
Name: GNOME Shell
Class: N/A
Window manager's "showing the desktop" mode: N/A

% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic

% uname -a
Linux ucbvax 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I just upgraded from 16.04 a couple of weeks ago. I think (90%) it was locking in 16.04, but now not locking in 18.04.

If I click on the upper-right-of-screen padlock icon, then the system does lock (password required).

While it's locked in that way, I can click on the upper-right-of-screen "suspend" (from drop-down), and then my system is both suspended and locked. But the question is ...

How can I make my system lock (automatically) every time a "suspend" happens? (Or even "every time kbd and mouse are idle for 15 minutes"?)

Please advise.

ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
 /dev/snd/controlC0: ubuntu 7633 F.... pulseaudio
 /dev/snd/controlC1: ubuntu 7633 F.... pulseaudio
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
 enp2s0 no wireless extensions.

 enp7s5 no wireless extensions.

 lo no wireless extensions.
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
Package: linux (not installed)
 PATH=(custom, no user)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
 linux-restricted-modules-4.15.0-29-generic N/A
 linux-backports-modules-4.15.0-29-generic N/A
 linux-firmware 1.173.1

Tags: bionic
Uname: Linux 4.15.0-29-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True 08/23/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0705
dmi.board.asset.tag: To be filled by O.E.M. M5A99X EVO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A99XEVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: To be filled by O.E.M. To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

Hello John,

Execute the following command in the terminal:

$ apport-collect -p linux 1798615

Best regards,
Cristian Aravena Romero (caravena)

affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
John Crown (jqc) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected bionic
description: updated
John Crown (jqc) wrote : CRDA.txt

apport information

apport information

John Crown (jqc) wrote : Lspci.txt

apport information

John Crown (jqc) wrote : Lsusb.txt

apport information

apport information

apport information

apport information

apport information

apport information

John Crown (jqc) wrote : UdevDb.txt

apport information

apport information

John Crown (jqc) wrote :

The apport-collect info (reflected above) was gathered while running in "try ubuntu" mode from the install media.

Before I ran apport-collect, I
1. gave the "Live session user" a password, and
2. confirmed that "Automatic Login" was OFF ; and
3. I verified that when I logged-out, I was required to enter a password; and
4. I verified that when I "suspended", no password was required.

in other words, the reported behavior is seen in the most basic configuration, namely, running from the install media.


Changed in linux (Ubuntu):
importance: Undecided → Medium
John Crown (jqc) wrote :

I believe this bug affects security, given that it is a failure of Ubuntu to perform a
"Session Lock". E.g. this is from NIST Special Publication 800-53 (Rev. 4):

  The information system:

    a. Prevents further access to the system by initiating a session lock
       after [Assignment: organization-defined time period] of inactivity or
       upon receiving a request from a user; and

    b. Retains the session lock until the user reestablishes access using
       established identification and authentication procedures.

The name has been changed from "Session Lock" to "Device Lock" in Rev 5
(draft, 2017), but it's still listed there for the sake of best practices.

Artur Kerge (krvl) wrote :

Experiencing same issue on 18.10 after upgrading from 18.04.
Several others are also having issues with locking as seen on this forum post:

Artur Kerge (krvl) wrote :

Issue has been resolved fore me with latest update. Thank you devs for your time and effort!

John Crown (jqc) wrote :

Confirming, issue is resolved for me (OP).
Sorry can't say exactly when the behavior changed, but now it's all good.

Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Omar Fitian (fofo-fit) on 2019-11-17
Changed in linux (Ubuntu):
status: Expired → Confirmed
Oz123 (nahumoz) wrote :

Dear Ubuntu team,
I don't know who sets the priority on bugs. But having this set as a medium priority means that Ubuntu isn't ready for the enterprise desktop.
Maybe it's not even your audience. But I can't used this OS as a Desktop for work purposes.
(Server is a different story... ).
It would be nice to see this propelry fixed.

John Crown (jqc) wrote :

I'm changing the status to "Fix Released", based on current behavior. (This is 18.04 with all available current updates.) (I can no longer reproduce this problem, so somebody must have fixed it!)

I probably should have done this status change on 2019-01-10 along with the note I added then, but I didn't know I had the juice.

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers