Cannot unlock lock screen

[jeremy-list]

To replicate:
Leave the computer unattended until the screen locks, then press some keys and click the mouse.

Expected results:
A password confirmation dialog should appear.

Actual results:
All mouse clicks and key presses are ignored except ctrl-alt-F1.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-settings-daemon 3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
Uname: Linux 4.12.0-13-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 21 15:39:09 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
InstallationDate: Installed on 2017-08-15 (36 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
SourcePackage: gnome-settings-daemon
UpgradeStatus: Upgraded to artful on 2017-09-14 (6 days ago)

[Sebastien Bacher (seb128)]

the log has errors about the stored configuration and the intel driver, unsure which one is to blame

[Daniel van Vugt (vanvugt)]

Your GUI is hanging

Sep 21 14:30:43 hostname org.gnome.Shell.desktop[2881]: Window manager warning: last_user_time (850630) is greater than comparison timestamp (850629). This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW. Trying to work around...

for apparently the same reasons as the kernel:

Sep 21 15:25:24 hostname kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=56315 end=56316) time 495 us, min 763, max 767, scanline start 762, end 786

which is a hardware/firmware bug (!?):

Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST: CPU0: -1008111239 force to 0
Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST differs: Reference CPU0: -1008111239 CPU1: 0
Sep 21 14:16:41 hostname kernel: #2
Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST differs: Reference CPU0: -1008111239 CPU2: 0
Sep 21 14:16:41 hostname kernel: #3
Sep 21 14:16:41 hostname kernel: [Firmware Bug]: TSC ADJUST differs: Reference CPU0: -1008111239 CPU3: 0

I've never seen this happen before but have encountered plenty of code over the years where such bugs were expected and had to be handled. It sounds like you may need a different kernel, different BIOS, or new firmware from Intel. It's certainly not gnome-shell's fault that it might hang in such a volatile environment.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1718573

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[jeremy-list (quick-dudley)]

I can no longer replicate this bug with the 4.13.0-12-generic kernel.