Screen not locked when coming out of suspend/hibernate
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm3 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
gnome-shell (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
When system returns from suspend mode, user is not prompted for password, so last thing that was active before suspending is visible, but clicking around does not work. Only thing that is clickable is top menu (network, sound, battery icons) but menu only opens and clicking further options is not possible. After that, I lock screen (win key + L) and main menu (with launch pad) is visible, clickable but anything I click is not visible while screen is locked (later, when I unlock screen, those app that I clicked are open). After unlocking screen, everything works normally.
Suspend is initiated using keyboard
This was not case before, but suddenly it started to behave like this, I don't know why, I don't remember installing anything.
1)Release of ubuntu :
Description: Ubuntu 18.04.1 LTS
Release: 18.04
2) I don't know which package is related to this
3) Expected behavior
I expected lock screen when system returns from suspend mode
4) What happens instead
Lock screen is not shown, and last screen where I was is shown (for example Chrome)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver (not installed)
ProcVersionSign
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 2 22:36:28 2019
InstallationDate: Installed on 2018-05-05 (301 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen not locked when coming out of suspend/hibernate
UpgradeStatus: No upgrade log present (probably fresh install)
affects: | gnome-screensaver (Ubuntu) → gnome-shell (Ubuntu) |
information type: | Private Security → Public Security |
Additional (maybe) useful info :
I remember that this bug started to happen when I started to use HDMI cable. Sometimes I suspend system while cable is still inside, and remove it while system is suspended.