** Description changed: I am experiencing a reproducible mouse/pointer input failure after suspend on Ubuntu 24.04 running GNOME Shell 46 under Wayland. After resuming from suspend, the mouse pointer still moves normally and hover effects work, but mouse button clicks are not delivered correctly to parts of the GNOME Shell UI. For example, the upper-right system menu and launcher/dock icons highlight when the pointer moves over them, but clicking does nothing. Touchscreen taps continue to work normally on the same UI elements. The physical mouse/input device itself appears to be functioning correctly. While the problem is occurring, `libinput debug-events` shows the expected mouse button press and release events (`POINTER_BUTTON` / `BTN_LEFT`), even though GNOME does not respond to the clicks. The issue can be reproduced without physically closing the laptop lid. Steps to reproduce: 1. Start a normal GNOME Wayland session. 2. Confirm mouse clicking works normally. 3. Run: systemctl suspend 4. Resume the computer. 5. Unlock the session. 6. Move the mouse over GNOME Shell UI elements and click them. Actual result: Pointer movement and hover highlighting work, but mouse clicks are not accepted correctly. Touchscreen input still works. Expected result: Mouse pointer movement and mouse button input should continue working normally after suspend/resume. Important observations: - Merely locking and unlocking the session with Super+L does NOT reproduce the problem. - The system must actually suspend/resume. - The issue reproduces using `systemctl suspend`, so it is not dependent on lid-close behavior or accidental touchscreen input while closing the lid. - The machine has a touchscreen. - Tiling Assistant is not required to reproduce the issue. - Mouse button events remain visible in `libinput debug-events` while the GUI ignores them. - Touchscreen taps continue functioning while mouse clicks do not. - No reboot or logout is required to recover. While the problem occurs, the GNOME Shell journal repeatedly contains an assertion from Mutter's Wayland pointer-focus code: meta_wayland_pointer_set_focus: assertion 'meta_cursor_tracker_get_pointer_visible (cursor_tracker) || clutter_seat_is_unfocus_inhibited (clutter_seat) || surface == NULL' failed A particularly useful observation is that switching from the graphical Wayland session to a virtual terminal and immediately back restores mouse clicking without restarting GNOME Shell or logging out. Recovery steps: Ctrl+Alt+F3 Wait a few seconds, then: Ctrl+Alt+F2 After switching back to the graphical session, mouse clicks immediately work normally again. This recovery is repeatable. Observed sequence: Working Wayland session | v systemctl suspend | v resume / unlock | v mouse pointer moves normally hover detection works libinput receives button presses/releases touchscreen input works mouse clicks are not delivered correctly | v Mutter logs meta_wayland_pointer_set_focus assertion | v switch to VT and back | v mouse input immediately works again This suggests that the physical input event is reaching libinput, but the Wayland pointer/focus state in Mutter is not being restored correctly after suspend/resume. System information: OS: Ubuntu 24.04 LTS Desktop: GNOME Shell 46.0 Session type: Wayland Touchscreen: Yes Additional command output: $ echo $XDG_SESSION_TYPE wayland $ gnome-shell --version GNOME Shell 46.0 I can reproduce this reliably and can provide additional Mutter/GNOME Shell journal output or perform additional diagnostic tests if needed. ``` ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 7.0.0-31.31~24.04.1-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Sep 19 12:27:15 2026 InstallationDate: Installed on 2025-08-25 (390 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) + + Additional potentially relevant information: + + I found recent reports of a very similar pointer-button failure after + suspend/resume under another Wayland compositor (KWin). + + In those reports: + + - pointer movement continues normally after resume + - pointer clicks stop being delivered + - multiple pointer devices can be affected simultaneously + - libinput continues receiving input + - resetting compositor/input-device state restores clicking + + For example: + https://bugs.kde.org/show_bug.cgi?id=524322 + https://bugs.kde.org/show_bug.cgi?id=525668 + + I understand these are KWin bugs and may have a different root cause, + but the suspend/resume failure pattern is very similar. + + In my GNOME/Mutter case, there is the additional diagnostic evidence + that GNOME Shell repeatedly logs: + + meta_wayland_pointer_set_focus: + assertion 'meta_cursor_tracker_get_pointer_visible (cursor_tracker) + || clutter_seat_is_unfocus_inhibited (clutter_seat) + || surface == NULL' failed + + and switching to another VT and back immediately restores pointer + clicking.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2167770 Title: Wayland mouse clicks stop being delivered after suspend; libinput receives clicks; touchscreen works; VT switch restores input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2167770/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
