I couldn't interact with the screenlock

[Seth Arnold]

Hello, I use i3lock to lock my screen. systemd starts gnome-screensaver when I suspend my laptop because I haven't figured out how to turn that off yet.

Most of the time this is no big deal, I just have to unlock twice the five or six times a year I suspend my laptop.

Today, however, I couldn't actually interact with the gnome-screensaver lock screen:

- I resumed my laptop
- I unlocked the already-running i3lock
- The gnome-screensaver was running, showed the correct time in the center of the 'titlebar', showed my user name in the right side of the titlebar, and the mouse moved around fine.
- I blindly typed my password and hit enter
- The mouse pointer turned to a spinner for 20~40 seconds
- The mouse pointer could move around, but couldn't interact with any screen elements
- ctrl+alt+f1 etc worked fine to change virtual consoles

I was only able to use my X11 session after manually killing the gnome-screensaver process from a shell.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Wed Jul 10 15:05:31 2019
InstallationDate: Installed on 2012-10-18 (2456 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
UpgradeStatus: Upgraded to bionic on 2018-05-02 (435 days ago)

[Seth Arnold (seth-arnold)]

Hmm. The process I killed was most definitely gnome-screensaver.

It might have been running in an LXD instance. This is strange.