My screen is unlocking without a password after being locked for an unknown time period, like a lunch break or overnight. It is not hibernating or suspending, just locked. If I lock it and immediately unlock it forces me to use password as it should, otherwise about 40% of the time it just unlocks to my full session as I left it before locking. I lock by physically clicking the lock icon in the top left of the screen. I've not tested by just walking away and waiting.
My screen is unlocking without a password after being locked for an unknown time period, like a lunch break or overnight. It is not hibernating or suspending, just locked. If I lock it and immediately unlock it forces me to use password as it should, otherwise about 40% of the time it just unlocks to my full session as I left it before locking. I lock by physically clicking the lock icon in the top left of the screen. I've not tested by just walking away and waiting.
I originally posted here https:/ /askubuntu. com/questions/ 1012420/ ubuntu- 17-10-major- security- issue-at- login?noredirec t=1#comment1641 885_1012420 if that helps.
Let me know other info you need to help find a fix. This is a major security issue for me at my location.
ProblemType: Bug ature: Ubuntu 4.13.0- 36.40-generic 4.13.13 eInhibited: No ibitors: None ession: desktop. session session-name 'ubuntu' desktop. session idle-delay uint32 300 256color DIR=<set>
DistroRelease: Ubuntu 17.10
Package: gnome-screensaver 3.6.1-7ubuntu6
ProcVersionSign
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 7 15:16:15 2018
GnomeSessionIdl
GnomeSessionInh
GsettingsGnomeS
org.gnome.
org.gnome.
InstallationDate: Installed on 2018-03-01 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen locking issue
UpgradeStatus: No upgrade log present (probably fresh install)