Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#75291 - [gnome] Wayland pointer stops working in windows after couple of seconds

Attached to Project: Arch Linux
Opened by Florian (nougad) - Sunday, 10 July 2022, 16:24 GMT
Last edited by Toolybird (Toolybird) - Monday, 08 August 2022, 03:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrade to Gnome 42 on Wayland when opening a window the mouse stops working inside the window after couple of seconds. The pointer can be moved but can't interact with the window (scroll, click, hover) or the window title bar. It can interact with the rest of the system (gnome bar at the top). It happens typically after 5-60s after opening the window. It happens in all kind of windows (Gnome settings, chrome, firefox, spotify, gnome Terminal). After closing the window and opening it again it works for a couple of seconds. It happens with Bluetooth mouse but also with built-in touchpad. It only affects wayland, running gnome with Xorg works fine. Systemd journal does not include any helpful information. libinput debug-events still shows the clicks but the window does not react to it anymore.

Steps to reproduce:

1. Open a window
2. Wait
3. Try to inside the window click -> does not work


Additional info:


In the screencast you see libinput detects the clicks but at some point the window stops responding to it:

I opened a ticket in upstream mutter but no response yet https://gitlab.gnome.org/GNOME/mutter/-/issues/2285. I have the bug already since a couple of months since gnome 42 was added to archlinux.
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 08 August 2022, 03:36 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Reporter says "Problem solved via `gsettings reset org.gnome.mutter check-alive-timeout`"
Comment by Florian (nougad) - Sunday, 10 July 2022, 16:26 GMT Comment by Toolybird (Toolybird) - Sunday, 07 August 2022, 22:57 GMT
Does this forum post [1] help?

[1] https://bbs.archlinux.org/viewtopic.php?id=276220
Comment by Florian (nougad) - Monday, 08 August 2022, 00:28 GMT
YES! it works !! `gsettings reset org.gnome.mutter check-alive-timeout` solved the problem

Loading...