GNOME becomes unresponsive after wiping down touchscreen

[Connor Nolan]

After I wiped down my laptop's touchscreen with a wipe, GNOME went to the "Activities" screen (I must've hit the button while wiping down the screen), then GNOME became unresponsive.

By unresponsive, I don't mean it froze. The mouse cursor still moved smoothly. It even recognized touch events by hiding the cursor when I tapped the screen. But it ignored literally everything else. The one other thing that changed the UI was changing my keyboard's backlight, which caused a volume-esque dialog to show up notifying me of the change, before quickly fading. I couldn't even use the Fn-Ctrl-Alt-X keys to switch to a TTY.

I then closed my laptop's lid to put it to sleep and reopened it a little while later. The lockscreen was perfectly functional, but once I logged back in, the problem remained. Although Fn-Ctrl-Alt-X keys worked again.

At that point I gave up and restarted my laptop. It's a good thing I didn't have anything important unsaved, or I could've just lost my data because I wiped down my touchscreen.

I'm using Ubuntu 22.04 Wayland, GNOME Shell 42.2 (according to gnome-shell --version).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-14 (493 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
Package: gnome-shell 42.2-0ubuntu0.2
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.17.0-1017.18-oem 5.17.15
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
Tags: wayland-session jammy
Uname: Linux 5.17.0-1017-oem x86_64
UpgradeStatus: Upgraded to jammy on 2022-05-10 (162 days ago)
UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1993592

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Connor Nolan (thebrokenrail)]

apport information

[Connor Nolan (thebrokenrail)]

apport information

[Connor Nolan (thebrokenrail)]

apport information

[Connor Nolan (thebrokenrail)]

apport information

[Connor Nolan (thebrokenrail)]

apport information

[Daniel van Vugt (vanvugt)]

Thanks. I wonder if these extensions are causing it:

  '<email address hidden>'
  '<email address hidden>'

Please start by deleting all local extensions:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

[Connor Nolan (thebrokenrail)]

'<email address hidden>' is actually a remnant from Ubuntu 20.04 and isn't enabled, and '<email address hidden>' is ridiculously simple and only messes with the a small portion of the OSK (https://github.com/lxylxy123456/cariboublocker/blob/master/42/extension.js). I wouldn't expect that to block *all* input. Also, I can't reproduce the issue, it just happened once while wiping down my screen.

[Daniel van Vugt (vanvugt)]

I know, that's what everyone says. But even a trivial extension can break the whole shell.

Next time the bug becomes an annoyance, please make deleting the extensions the first thing you try.

[Daniel van Vugt (vanvugt)]

The second (or parallel) thing to try is to check for some component crashing:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Launchpad Janitor (janitor)]

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