Login screen sometimes unresponsive to mouse clicks (after waking from sleep)

[Daniel van Vugt]

The login screen is sometimes unresponsive to mouse clicks (after waking from sleep).

I can generally get it working again either by hitting Tab, or by switching VTs.

Seems to happen with either Wayland or Xorg greeters.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
Uname: Linux 5.15.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Mar 16 14:07:16 2022
DisplayManager: gdm3
InstallationDate: Installed on 2021-11-05 (130 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103)
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

[Paul White (paulw2u)]

I can confirm this as twice I've had difficulties logging in after waking from sleep and once after a 40 minute period of the screen being locked while I was away from the PC. This is using Wayland.

I have a dual monitor set-up and see a mouse pointer on both screens. Each time I have had to switch to a vt, switch back to vt1 and then log-in. The effects of pressing tab or escape have been quite random. On one occasion I could see my desktop but could not actually use it and on another I could see Ubuntu Dock on top of the lock screen but could not log in.

[Daniel van Vugt (vanvugt)]

Maybe related to bug 1964545 somehow?

[corrado venturini (corradoventu)]

Sometimes after waking from sleep i have a black screen unresponsive to mouse click or any key, I see the disk led blinking and nothing more. Only poweroff allow exiting.

[Daniel van Vugt (vanvugt)]

That's a different issue so please open a new bug.

[Paul White (paulw2u)]

Just an update to my comment #2.

Changing to a single monitor set-up I'm seeing the reported problem without any of the side effects that I reported while using dual monitors.

I don't see this as an issue that is related to a PC being put into sleep mode as any short or long duration of the lock screen being invoked for has, on my laptop, seen this bug make an appearance.

[Olivier Tilloy (osomon)]

I'm seeing the same symptoms as Corrado (comment #4). After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1.

That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily).

Daniel, I can file a separate bug if you think it deserves one, but it has enough similarities with the description that I thought I'd first comment here. I'm also happy to help debugging the problem and/or test potential fixes.

[Olivier Tilloy (osomon)]

I read again the description and it says the login screen is unresponsive, not that the screen doesn't wake up. Additionally the tab key doesn't work to wake the screen for me, only Ctrl+Alt+F1. So it is a different bug after all. I'll file a new one.

[Olivier Tilloy (osomon)]

Done: bug #1968040.

[Daniel van Vugt (vanvugt)]

Incomplete: No bug observed for days/weeks.

[Daniel van Vugt (vanvugt)]

Looks like it was https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5124

Fixed in mutter 42.1 and in Ubuntu via clutter-stage-Repick-when-pointer-actor-goes-unmapped.patch