After update, Login no longer works after waking from 'systemctl suspend'

[John Grady]

Updated 22.04.4 LTS today (4/9/24).

After the update, the login screen coming out of being suspended (systemctl suspend) doesn't accept a password. Meaning that no characters typed show up in the password box. Like the password box doesn't, or can't get, focus. This prevents using the computer after suspending, and requires a reboot to get back into the desktop.

All worked properly before today's update. Meaning that after coming out of suspension I was able to click in the password box, type in my password, and gain entry back to the desktop and continue my work.

Steps are:
   Update Ubuntu using 'Software Updater'
   Reboot required to finish update
   Suspend computer using 'systemctl suspend' at command line
   Close computer lid
   --- After a few minutes ---
   Open lid
   Computer wakes up and login screen is displayed with the current user and password entry box.

At this point the password box doesn't appear to receive focus and I can't type into it.
I've tried tabbing and mouse clicking, but can't type into the password entry box.
I've tried just typing my password and hitting the enter key as if it was accepting input but just not echoing it, but that doesn't work either.
I've also rerun the updater to make sure everything is up-to-date and it says that there are no other updates.

This problem results in not being able to resume working on the machine after suspending it. So I have to restart the computer.

Thanks for your time,
John

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 5.15.0-102.112-generic 5.15.148
Uname: Linux 5.15.0-102-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 9 14:20:08 2024
InstallationDate: Installed on 2019-01-03 (1923 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to jammy on 2022-08-14 (604 days ago)
VarLogDistupgradeTermlog:

mtime.conffile..etc.update-manager.release-upgrades: 2019-05-12T20:41:04.743940

[Ganton (ganton)]

If you use an external keyboard, do you have the same problem?

[John Grady (jgrady42)]

Sorry for the delay.  I had to find an external keyboard and a usb-c
adapter.

I can connect the external keyboard and switch it in and out ad-hoc and
my laptop keyboard and the external keyboard both work fine.  So base
case is good.

I can suspend the computer with the laptop keyboard and, upon waking,
the laptop keyboard does not type characters into the password box.
Then I connect the external keyboard and I CAN enter the password and
get to the desktop.
Once I disconnect the external keyboard the laptop's keyboard still does
not enter characters at the command prompt (after logging in with the
external keyboard after waking up after a suspend).
I reconnect the external keyboard and I can then resume working.

It appears that suspending the laptop somehow is disabling the laptop's
keyboard.

Note that the functionality of the laptop's mouse is unaffected.

I hope this helps,
John

If there's any other tests you'd like me to run, please let me know.
(but I won't be able to run them until tomorrow morning.)

On 4/9/24 15:13, Ganton wrote:
> If you use an external keyboard, do you have the same problem?
>

[Ganton (ganton)]

> I can suspend the computer with the laptop keyboard and, upon waking,
> the laptop keyboard does not type characters into the password box.
> Then I connect the external keyboard and I CAN enter the password and
> get to the desktop.

This recent bug report is possibly related:

The keyboard does not work after latest kernel update
https://bugs.launchpad.net/ubuntu/+bug/2060727

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2060736/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Viacheslav Modestov (dobhareach)]

Original report: https://bugs.launchpad.net/ubuntu/+bug/2060736

[Viacheslav Modestov (dobhareach)]

Changed report to lightdm package: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2060736