Mouse cannot control windows after suspend and display change

[Thomas M Steenholdt]

My setup is this:

Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
Display: Lenovo T34w-20, connected via USB-C

The problem started with upgrade to 22.04
I have had the same exact problem with my previous laptop, a ThinkPad T14s. Both of these are AMD laptops, but I had no problem on 21.10.

Way I can usually reproduce (always?)

1. Suspend my laptop by yanking out the USB-C cable.
2. Resume the laptop by connecting a different monitor (same make and model, but not the same physical one) and hit the keyboard a few times.

Note: Resuming on the same physical display does not seem to result in the same problem.

After this, I can no longer control the Windows on my desktop. The mouse cursor is active, but moves behind the open windows, and mouse click is not registered (at least not in a way that is useful).

I can navigate the windows and use the applications, using the keyboard.

Ctrl+Alt+F1 to get to GDM, the mouse works fine. Going back the the real session, mouse is still "broken".

Ctrl+Alt+F2 to get to a TTY, and going back to the original session, mouse is still "broken".

Only way I have found to reliably restore functionality is a reboot (which I have been doing a lot of the last few months).

Please let me know what else I can provide you with, in order to get this fixed. :)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Fri Aug 19 10:32:48 2022
InstallationDate: Installed on 2022-05-20 (91 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thanks for the bug report. Next time the problem happens, please:

1. Wait 10 seconds.

2. Log into a TTY: Ctrl+Alt+F4

3. Run:

   sync
   lspci -k > lspci.txt
   journalctl -b0 > journal.txt

4. Reboot.

5. Attach the resulting text files here.

[Daniel van Vugt (vanvugt)]

Please also check for crashes:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

[Thomas M Steenholdt (tmus)]

Thanks for the directions...

It's not that hard to reproduce here, I just have to move between places (or I could bring my other monitor closer, for more intense troubleshooting if need be). But it just happened...

There are no recent crashes and nothing reported by whoopsie. The requested files are attached.

[Thomas M Steenholdt (tmus)]

journalctl -b0

[Thomas M Steenholdt (tmus)]

lspci -k

[Launchpad Janitor (janitor)]

[Expired for mutter (Ubuntu) because there has been no activity for 60 days.]